--
--
Google & Yahoo Bulk Senders Compliance Audit
Strict evaluation of authentication policies and bulk delivery requirements
Mail Authentication (SPF / DMARC / DKIM)
RFC 7208 / 7489TLS Encryption & Perimeter HTTP Headers
Transport SecurityBlacklist Reputation Matrix (Direct DNSBL)
Real-time IP VerificationDNS Resilience & BGP ASN/Operator Diversity (RFC 2182)
| Nameserver (NS) | IP Address | ASN | Operator / BGP Network |
|---|---|---|---|
| No scan data available... | |||
SMTP Security & MTA-STS (Port 25)
RFC 8461 / RFC 8460DNSSEC Integrity, DANE & CNAME Hygiene
Crypto & SubdomainsPerimeter Standards Technical Documentation
RFC specifications for mail server configuration and web security.
Publication of authorized sending mechanisms (ip4, mx, include). The strict limit is 10 DNS Lookups. Exceeding this limit forces a PermError resolution, causing legitimate emails to be dropped.
Requires domain alignment between SPF/DKIM and the From: header. Directives dictate receiver action: p=none (monitoring), p=quarantine (quarantine), and p=reject (immediate block).
Prevents Man-in-the-Middle attacks and TLS downgrade via policies in .well-known/mta-sts.txt and failure reports in _smtp._tls.
Requires geographic and infrastructure distribution of NS authoritative servers across multiple Autonomous Systems (ASNs) to prevent single points of failure (SPOF).