MX records (mail servers)
The MX records that name the servers taking mail for this domain. None at all means the domain does not receive mail — which is a decision, not a fault.
MX (mail exchanger) records tell the rest of the internet which servers accept email for a domain, and in what order of preference. A message to info@example.com is delivered by looking up the MX records of example.com and handing the mail to the server with the lowest priority number that answers.
What the row means
SiteScan looks up the MX records of the registrable domain (for shop.example.com, that is example.com) through a public DNS-over-HTTPS resolver. With one or more records the row is green and shows how many there are. With none it reads "No mail on this domain" as a neutral fact: plenty of domains — landing pages, redirect domains, project sites — deliberately do not receive mail. The mail-only records further down (MTA-STS, TLS-RPT, BIMI) appear only when MX records exist.
What to check
- If you expect mail, at least two MX hosts, or a provider whose single hostname is itself redundant, keep delivery going during an outage.
- Every MX must point at a hostname with an A or AAAA record, never directly at an IP address or at a CNAME.
- A domain that sends no mail should still publish
v=spf1 -allas its SPF record and a DMARC policy ofp=reject, so nobody can send mail in its name.
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 “DNS & email”
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