publicrecordsdata.us

We performed a comprehensive analysis of publicrecordsdata.us on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 10753ms. The page is served over HTTP/2 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 93 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Amazon (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 2027-03-05, which is 248 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 6 technologies across 5 categories powering publicrecordsdata.us. The detected stack includes Next.js css, Google Analytics 4, Microsoft Clarity, Google Tag Manager, Google AdSense, and LiveChat. The site uses Next.js as its primary framework (version css). Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, publicrecordsdata.us receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, publicrecordsdata.us receives a trust score of 80/100, which places it in the "Very 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 Amazon with 248 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine policy. 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 publicrecordsdata.us 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 publicrecordsdata.us and identified 6 distinct technologies across 5 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 css) — provides the application framework and routing for publicrecordsdata.us. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for publicrecordsdata.us. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for publicrecordsdata.us. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for publicrecordsdata.us. Chat: LiveChat — provides live chat and customer communication for publicrecordsdata.us. We also extracted the following tracking identifiers: Google Tag Manager container GTM-KBM3RRQR. These IDs can be used to identify other websites operated by the same organization.

publicrecordsdata.us delivers its homepage in 10753ms (server response time), which is considered slow by industry standards. The total page weight is 93 KB, and we detected 28 resource requests loading assets from 6 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. No compression is currently enabled on publicrecordsdata.us. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 1 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 2 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. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of publicrecordsdata.us produces approximately 0.05g 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 93 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for publicrecordsdata.us. 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.

publicrecordsdata.us resolves to the IPv4 address 13.33.235.129, 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 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1055.awsdns-03.org, ns-1915.awsdns-47.co.uk, ns-376.awsdns-47.com, and ns-529.awsdns-02.net. Having 4 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 publicrecordsdata.us is handled by emailsrvr.com with 2 MX records configured: mx1.emailsrvr.com and mx2.emailsrvr.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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 publicrecordsdata.us. 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 publicrecordsdata.us contains 738 words of visible text content. This is a moderate amount of content. The page is structured with 1 H2 headings, 1 H3 headings, 0 H4 headings. The link structure consists of 6 internal links pointing to other pages on the same domain and 4 external links pointing to third-party websites. There are 1 external JavaScript files, 1 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), and Schema.org structured data (Answer, ContactPoint, Country, FAQPage, ImageObject, OpeningHoursSpecification, Organization, Question, and WebSite). The website has social media presence across 2 platforms: Facebook (@publicrecordsdata.us) and Linkedin (@publicrecordsdata-us). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for publicrecordsdata.us is well-optimized at 44 characters: "Public Records Search | PublicRecordsData.us". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 160 characters (acceptable): "Search public records by name to access court records, property history, contact details, and background information fro...". 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 canonical url is correctly set to https://www.publicrecordsdata.us, preventing duplicate content issues, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Search public records by name to access court records, prope..."), OG description, OG image (social sharing thumbnail), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: Answer, ContactPoint, Country, FAQPage, ImageObject, OpeningHoursSpecification, Organization, Question, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.