dnsbl.info

We performed a comprehensive analysis of dnsbl.info on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 11228ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 15 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 Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-30, which is 60 days from now. The security headers analysis reveals a score of 15/100 (poor). The following security headers are properly configured: X-Frame-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, Referrer-Policy, and Permissions-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 1 technologies across 1 categories powering dnsbl.info. The detected stack includes Google Analytics 4. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, dnsbl.info receives an overall trust score of 70/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, dnsbl.info receives a trust score of 70/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, a valid SSL certificate issued by Google Trust Services with 60 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DNSSEC providing authenticated DNS responses, and a well-established domain registered for over 23.6 years, indicating long-term commitment and legitimacy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked dnsbl.info 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. The domain is registered through Tucows Domains Inc. based in CA, with a registration date of 2002-12-04 and expiration date of 2034-12-04.

Our technology detection engine scanned dnsbl.info and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for dnsbl.info. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-LVLBPDMV6W. These IDs can be used to identify other websites operated by the same organization.

dnsbl.info delivers its homepage in 11228ms (server response time), which is considered slow by industry standards. The total page weight is 15 KB, and we detected 22 resource requests loading assets from 4 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 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 dnsbl.info produces approximately 0.01g 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 15 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for dnsbl.info. 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.

dnsbl.info resolves to the IPv4 address 104.18.17.204, 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: lucy.ns.cloudflare.com and simon.ns.cloudflare.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 dnsbl.info is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for dnsbl.info, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. The domain is registered through Tucows Domains Inc. (CA). It was first registered on 2002-12-04 and is set to expire on 2034-12-04, making it 23.6 years old. Our subdomain enumeration scan discovered 1 active subdomains for dnsbl.info: www.dnsbl.info. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of dnsbl.info contains 617 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 4 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 12 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 1 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 website has social media presence across 2 platforms: Facebook (@dnsblinfo) and Twitter (@dnsblinfo). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for dnsbl.info is well-optimized at 53 characters: "DNSBL Information - Spam Database and Blacklist Check". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 179 characters (slightly long): "DNS-based block list information/database. Resource to find out information on DNS block lists and check IPs to see if ...". 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.dnsbl.info/, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to noarchive, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to dnsbl.info 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. The meta keywords tag contains 25 terms including dnsbl, black, block, list, and blacklist. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.