row.pro

We performed a comprehensive analysis of row.pro on 2026-07-06. The website returned an HTTP 200 status code with a server response time of 5920ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 38 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-10-04, which is 90 days from now. The security headers analysis reveals a score of 80/100 (good). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Content-Security-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 3 technologies across 3 categories powering row.pro. The detected stack includes Next.js chunks, React, and Google Analytics 4. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, row.pro receives an overall trust score of 77/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, row.pro receives a trust score of 77/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 90 days until expiration, and SPF (Sender Policy Framework) email authentication preventing email spoofing. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked row.pro against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned row.pro and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version chunks) — provides the application framework and routing for row.pro. UI Library: React — handles the user interface rendering and component management for row.pro. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for row.pro. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-3DESC1BZGC. These IDs can be used to identify other websites operated by the same organization.

row.pro delivers its homepage in 5920ms (server response time), which is considered slow by industry standards. The total page weight is 38 KB, and we detected 31 resource requests loading assets from 2 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 0 out of 1 CSS files and 0 out of 18 JavaScript files are minified. Minifying the remaining 19 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of row.pro produces approximately 0.02g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 38 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for row.pro. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

row.pro resolves to the IPv4 address 216.150.1.193, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: ns1.vercel-dns.com and ns2.vercel-dns.com. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for row.pro is handled by improvmx.com with 2 MX records configured: mx1.improvmx.com and mx2.improvmx.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for row.pro. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.

The homepage of row.pro contains 86 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 6 internal links pointing to other pages on the same domain and 3 external links pointing to third-party websites. There are 18 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for row.pro is well-optimized at 43 characters: "Row Pro — Mailing lists, from $0.01 per row". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 144 characters (well-optimized): "Pick who you want to mail. Download a CSV with names and verified mailing addresses. $0.08 per row, dropping to $0.01 at...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The page language is declared as en and a favicon is configured. No Open Graph tags are configured. When someone shares a link to row.pro on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.