DNS blocklist (DNSBL) check
Whether the address the site is served from appears on public DNS blocklists. A listing gets mail from that host filtered and can follow the site around.
DNS blocklists (DNSBL) are public databases of IP addresses and domains seen sending spam, hosting malware or phishing. Mail servers, firewalls and filters query them in real time. If the address your site is served from, or your domain itself, is listed, mail from it lands in spam or is refused, and some corporate networks block the site. A listing often comes from a compromised form, a hacked plugin, or a previous tenant of a shared IP.
How SiteScan checks it
The scanner looks up the server's IPv4 address in Spamhaus ZEN, SpamCop and UCEPROTECT, and the registered domain in Spamhaus DBL, SURBL and URIBL. Many lists refuse queries from public resolvers; a refusal is not counted as a clean result, which is why the green row says how many lists actually answered. Google Safe Browsing is counted among them when it is available. A listing turns the row red and names each list with the reason it gave.
What to do if listed
Find and fix the cause first: check mail logs, contact forms, outdated plugins and outgoing traffic. Then use each list's own lookup page to request removal — Spamhaus and SpamCop delist quickly once the problem stops; some lists expire entries on their own. On shared hosting, ask the provider for a clean IP. For mail, also set up SPF and DMARC.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Delivery & reputation”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data