Identity
56
F
spankbang.com
Posture Score: 49/100
Scanned May 28, 2026 at 2:59 AM UTC
Attack Surface
0
Reputation
92
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.spankbang.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@spankbang.com").
Weak DKIM RSA key (~1296 bits) for selector 's2'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.spankbang.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@spankbang.com").
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (40 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
MX records are valid
All MX records are properly configured.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on spankbang-com.mail.protection.outlook.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2405039672, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-responsive IP for www.spankbang.com: 2606:4700::6813:ef9c
The subdomain www.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for www.spankbang.com.
Non-responsive IP for www.spankbang.com: 2606:4700::6812:60f2
The subdomain www.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for www.spankbang.com.
Non-responsive IP for ftp.spankbang.com: 2606:4700::6813:ef9c
The subdomain ftp.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for ftp.spankbang.com.
Non-responsive IP for ftp.spankbang.com: 2606:4700::6812:60f2
The subdomain ftp.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for ftp.spankbang.com.
Non-responsive IP for ns1.spankbang.com: 2606:4700::6813:ef9c
The subdomain ns1.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for ns1.spankbang.com.
Non-responsive IP for ns1.spankbang.com: 2606:4700::6812:60f2
The subdomain ns1.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for ns1.spankbang.com.
Non-responsive IP for ns2.spankbang.com: 2606:4700::6813:ef9c
The subdomain ns2.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for ns2.spankbang.com.
Non-responsive IP for ns2.spankbang.com: 2606:4700::6812:60f2
The subdomain ns2.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for ns2.spankbang.com.
Non-responsive IP for vpn.spankbang.com: 2606:4700::6812:60f2
The subdomain vpn.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for vpn.spankbang.com.
Non-responsive IP for vpn.spankbang.com: 2606:4700::6813:ef9c
The subdomain vpn.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for vpn.spankbang.com.
Non-responsive IP for remote.spankbang.com: 2606:4700::6813:ef9c
The subdomain remote.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for remote.spankbang.com.
Non-responsive IP for remote.spankbang.com: 2606:4700::6812:60f2
The subdomain remote.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for remote.spankbang.com.
Non-responsive IP for admin.spankbang.com: 2606:4700::6812:60f2
The subdomain admin.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for admin.spankbang.com.
Non-responsive IP for admin.spankbang.com: 2606:4700::6813:ef9c
The subdomain admin.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for admin.spankbang.com.
Non-responsive IP for portal.spankbang.com: 2606:4700::6812:60f2
The subdomain portal.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for portal.spankbang.com.
Non-responsive IP for portal.spankbang.com: 2606:4700::6813:ef9c
The subdomain portal.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for portal.spankbang.com.
Non-responsive IP for dev.spankbang.com: 2606:4700::6812:60f2
The subdomain dev.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for dev.spankbang.com.
Non-responsive IP for dev.spankbang.com: 2606:4700::6813:ef9c
The subdomain dev.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for dev.spankbang.com.
Non-responsive IP for staging.spankbang.com: 2606:4700::6813:ef9c
The subdomain staging.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for staging.spankbang.com.
Non-responsive IP for staging.spankbang.com: 2606:4700::6812:60f2
The subdomain staging.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for staging.spankbang.com.
Non-responsive IP for test.spankbang.com: 2606:4700::6813:ef9c
The subdomain test.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for test.spankbang.com.
Non-responsive IP for test.spankbang.com: 2606:4700::6812:60f2
The subdomain test.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for test.spankbang.com.
Non-responsive IP for api.spankbang.com: 2606:4700::6813:ef9c
The subdomain api.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for api.spankbang.com.
Non-responsive IP for api.spankbang.com: 2606:4700::6812:60f2
The subdomain api.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for api.spankbang.com.
Non-responsive IP for app.spankbang.com: 2606:4700::6813:ef9c
The subdomain app.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for app.spankbang.com.
Non-responsive IP for app.spankbang.com: 2606:4700::6812:60f2
The subdomain app.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for app.spankbang.com.
Non-responsive IP for cdn.spankbang.com: 2606:4700::6813:ef9c
The subdomain cdn.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for cdn.spankbang.com.
Non-responsive IP for cdn.spankbang.com: 2606:4700::6812:60f2
The subdomain cdn.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for cdn.spankbang.com.
Non-responsive IP for blog.spankbang.com: 2606:4700::6813:ef9c
The subdomain blog.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for blog.spankbang.com.
Non-responsive IP for blog.spankbang.com: 2606:4700::6812:60f2
The subdomain blog.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for blog.spankbang.com.
Non-responsive IP for shop.spankbang.com: 2606:4700::6812:60f2
The subdomain shop.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for shop.spankbang.com.
Non-responsive IP for shop.spankbang.com: 2606:4700::6813:ef9c
The subdomain shop.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for shop.spankbang.com.
Non-responsive IP for store.spankbang.com: 2606:4700::6812:60f2
The subdomain store.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for store.spankbang.com.
Non-responsive IP for store.spankbang.com: 2606:4700::6813:ef9c
The subdomain store.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for store.spankbang.com.
Non-responsive IP for support.spankbang.com: 2606:4700::6813:ef9c
The subdomain support.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for support.spankbang.com.
Non-responsive IP for support.spankbang.com: 2606:4700::6812:60f2
The subdomain support.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for support.spankbang.com.
Non-responsive IP for help.spankbang.com: 2606:4700::6813:ef9c
The subdomain help.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for help.spankbang.com.
Non-responsive IP for help.spankbang.com: 2606:4700::6812:60f2
The subdomain help.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for help.spankbang.com.
Non-responsive IP for docs.spankbang.com: 2606:4700::6812:60f2
The subdomain docs.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for docs.spankbang.com.
Non-responsive IP for docs.spankbang.com: 2606:4700::6813:ef9c
The subdomain docs.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for docs.spankbang.com.
Non-responsive IP for status.spankbang.com: 2606:4700::6812:60f2
The subdomain status.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for status.spankbang.com.
Non-responsive IP for status.spankbang.com: 2606:4700::6813:ef9c
The subdomain status.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for status.spankbang.com.
Non-responsive IP for git.spankbang.com: 2606:4700::6813:ef9c
The subdomain git.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for git.spankbang.com.
Non-responsive IP for git.spankbang.com: 2606:4700::6812:60f2
The subdomain git.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for git.spankbang.com.
Non-responsive IP for ci.spankbang.com: 2606:4700::6812:60f2
The subdomain ci.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for ci.spankbang.com.
Non-responsive IP for ci.spankbang.com: 2606:4700::6813:ef9c
The subdomain ci.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for ci.spankbang.com.
Non-responsive IP for jenkins.spankbang.com: 2606:4700::6812:60f2
The subdomain jenkins.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for jenkins.spankbang.com.
Non-responsive IP for jenkins.spankbang.com: 2606:4700::6813:ef9c
The subdomain jenkins.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for jenkins.spankbang.com.
Non-responsive IP for grafana.spankbang.com: 2606:4700::6813:ef9c
The subdomain grafana.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for grafana.spankbang.com.
Non-responsive IP for grafana.spankbang.com: 2606:4700::6812:60f2
The subdomain grafana.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for grafana.spankbang.com.
Non-responsive IP for prometheus.spankbang.com: 2606:4700::6812:60f2
The subdomain prometheus.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for prometheus.spankbang.com.
Non-responsive IP for prometheus.spankbang.com: 2606:4700::6813:ef9c
The subdomain prometheus.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for prometheus.spankbang.com.
Non-responsive IP for kibana.spankbang.com: 2606:4700::6813:ef9c
The subdomain kibana.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for kibana.spankbang.com.
Non-responsive IP for kibana.spankbang.com: 2606:4700::6812:60f2
The subdomain kibana.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for kibana.spankbang.com.
Non-responsive IP for elastic.spankbang.com: 2606:4700::6813:ef9c
The subdomain elastic.spankbang.com resolves to 2606:4700::6813:ef9c which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6813:ef9c is operational or remove the DNS record for elastic.spankbang.com.
Non-responsive IP for elastic.spankbang.com: 2606:4700::6812:60f2
The subdomain elastic.spankbang.com resolves to 2606:4700::6812:60f2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:60f2 is operational or remove the DNS record for elastic.spankbang.com.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
0 subdomain(s) discovered for spankbang.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for spankbang.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.spankbang.com, resolving to 104.18.96.242, 104.19.239.156. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.spankbang.com is active and requires authentication.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain spankbang.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on spankbang.com
Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
HSTS enabled with preload on webmail.spankbang.com
Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
security.txt present
Found security.txt at https://spankbang.com/.well-known/security.txt.
TLS certificate valid for 53 days
Certificate for spankbang.com expires on 2026-07-20.
Certificate issued by E8
The certificate for spankbang.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for spankbang.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for spankbang.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for spankbang.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on spankbang.com.
Domain valid for 267 days
Domain spankbang.com expires on 2027-02-19.
No disposable email provider MX records
MX records for spankbang.com do not match known disposable email provider patterns.
Domain is 5576 days old
Domain spankbang.com was registered 2011-02-19.
No wildcard MX records
No wildcard MX records detected for spankbang.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (spankbang-com.mail.protection.outlook.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (spankbang-com.mail.protection.outlook.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
WHOIS registration data
Registrar: NameCheap, Inc. | Created: 2011-02-19 | Expires: 2027-02-19 | Updated: 2026-01-13
WHOIS privacy protection enabled
Domain spankbang.com has WHOIS privacy/redaction enabled.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: spanbang.com (has MX!), spnakbang.com (has MX!), spankabng.com (has MX!), spankbnag.com (has MX!), apankbang.com (has MX!)
29 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 29. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy missing
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: spankbang-com.mail.protection.outlook.com
PTR record proves mail server legitimacy
MX: spankbang-com.mail.protection.outlook.com
Mail server at 52.101.68.0
→
PTR Record
Reverse DNS: mail-db3pr0202cu00100.inbound.protection.outlook.com
Mail Server Reputation: spankbang-com.mail.protection.outlook.com
RBL check ensures server is not blacklisted
MX: spankbang-com.mail.protection.outlook.com
Mail server at 52.101.68.0
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✗
BIMI Record
✗
CAA Records
✗
DNSSEC
✓
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/spankbang.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan spankbang.com Again