Identity
20
F
com.com
Posture Score: 22/100
Scanned May 30, 2026 at 7:59 AM UTC
Attack Surface
0
Reputation
47
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.com.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@com.com").
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
Overly broad CIDR range: fd1d:f5c3:e7c6::/48
The /48 CIDR block authorizes a very large IP range to send email as this domain.
💡 Narrow the IP range to only the specific servers that send email.
No STARTTLS support on gator4018.hostgator.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
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.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.com.com
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.com.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@com.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
SPF record length OK (35 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.
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.
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 gator4018.hostgator.com
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2403306873, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive IP for www.com.com: 2606:4700:20::681a:594
The subdomain www.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for www.com.com.
Non-responsive IP for www.com.com: 2606:4700:20::ac43:48da
The subdomain www.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for www.com.com.
Non-responsive IP for www.com.com: 2606:4700:20::681a:494
The subdomain www.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for www.com.com.
Non-responsive IP for ftp.com.com: 2606:4700:20::681a:594
The subdomain ftp.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for ftp.com.com.
Non-responsive IP for ftp.com.com: 2606:4700:20::ac43:48da
The subdomain ftp.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for ftp.com.com.
Non-responsive IP for ftp.com.com: 2606:4700:20::681a:494
The subdomain ftp.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for ftp.com.com.
Non-responsive IP for ns1.com.com: 2606:4700:20::681a:494
The subdomain ns1.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for ns1.com.com.
Non-responsive IP for ns1.com.com: 2606:4700:20::ac43:48da
The subdomain ns1.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for ns1.com.com.
Non-responsive IP for ns1.com.com: 2606:4700:20::681a:594
The subdomain ns1.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for ns1.com.com.
Non-responsive IP for ns2.com.com: 2606:4700:20::681a:594
The subdomain ns2.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for ns2.com.com.
Non-responsive IP for ns2.com.com: 2606:4700:20::681a:494
The subdomain ns2.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for ns2.com.com.
Non-responsive IP for ns2.com.com: 2606:4700:20::ac43:48da
The subdomain ns2.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for ns2.com.com.
Non-responsive IP for vpn.com.com: 2606:4700:20::ac43:48da
The subdomain vpn.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for vpn.com.com.
Non-responsive IP for vpn.com.com: 2606:4700:20::681a:594
The subdomain vpn.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for vpn.com.com.
Non-responsive IP for vpn.com.com: 2606:4700:20::681a:494
The subdomain vpn.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for vpn.com.com.
Non-responsive IP for remote.com.com: 2606:4700:20::681a:494
The subdomain remote.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for remote.com.com.
Non-responsive IP for remote.com.com: 2606:4700:20::681a:594
The subdomain remote.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for remote.com.com.
Non-responsive IP for remote.com.com: 2606:4700:20::ac43:48da
The subdomain remote.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for remote.com.com.
Non-responsive IP for admin.com.com: 2606:4700:20::681a:494
The subdomain admin.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for admin.com.com.
Non-responsive IP for admin.com.com: 2606:4700:20::681a:594
The subdomain admin.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for admin.com.com.
Non-responsive IP for admin.com.com: 2606:4700:20::ac43:48da
The subdomain admin.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for admin.com.com.
Non-responsive IP for portal.com.com: 2606:4700:20::681a:594
The subdomain portal.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for portal.com.com.
Non-responsive IP for portal.com.com: 2606:4700:20::681a:494
The subdomain portal.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for portal.com.com.
Non-responsive IP for portal.com.com: 2606:4700:20::ac43:48da
The subdomain portal.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for portal.com.com.
Non-responsive IP for dev.com.com: 2606:4700:20::681a:494
The subdomain dev.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for dev.com.com.
Non-responsive IP for dev.com.com: 2606:4700:20::681a:594
The subdomain dev.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for dev.com.com.
Non-responsive IP for dev.com.com: 2606:4700:20::ac43:48da
The subdomain dev.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for dev.com.com.
Non-responsive IP for staging.com.com: 2606:4700:20::681a:494
The subdomain staging.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for staging.com.com.
Non-responsive IP for staging.com.com: 2606:4700:20::ac43:48da
The subdomain staging.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for staging.com.com.
Non-responsive IP for staging.com.com: 2606:4700:20::681a:594
The subdomain staging.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for staging.com.com.
Non-responsive IP for test.com.com: 2606:4700:20::681a:494
The subdomain test.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for test.com.com.
Non-responsive IP for test.com.com: 2606:4700:20::ac43:48da
The subdomain test.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for test.com.com.
Non-responsive IP for test.com.com: 2606:4700:20::681a:594
The subdomain test.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for test.com.com.
Non-responsive IP for api.com.com: 2606:4700:20::ac43:48da
The subdomain api.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for api.com.com.
Non-responsive IP for api.com.com: 2606:4700:20::681a:494
The subdomain api.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for api.com.com.
Non-responsive IP for api.com.com: 2606:4700:20::681a:594
The subdomain api.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for api.com.com.
Non-responsive IP for app.com.com: 2606:4700:20::681a:494
The subdomain app.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for app.com.com.
Non-responsive IP for app.com.com: 2606:4700:20::681a:594
The subdomain app.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for app.com.com.
Non-responsive IP for app.com.com: 2606:4700:20::ac43:48da
The subdomain app.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for app.com.com.
Non-responsive IP for cdn.com.com: 2606:4700:20::ac43:48da
The subdomain cdn.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for cdn.com.com.
Non-responsive IP for cdn.com.com: 2606:4700:20::681a:494
The subdomain cdn.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for cdn.com.com.
Non-responsive IP for cdn.com.com: 2606:4700:20::681a:594
The subdomain cdn.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for cdn.com.com.
Non-responsive IP for blog.com.com: 2606:4700:20::ac43:48da
The subdomain blog.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for blog.com.com.
Non-responsive IP for blog.com.com: 2606:4700:20::681a:494
The subdomain blog.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for blog.com.com.
Non-responsive IP for blog.com.com: 2606:4700:20::681a:594
The subdomain blog.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for blog.com.com.
Non-responsive IP for shop.com.com: 2606:4700:20::681a:494
The subdomain shop.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for shop.com.com.
Non-responsive IP for shop.com.com: 2606:4700:20::681a:594
The subdomain shop.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for shop.com.com.
Non-responsive IP for shop.com.com: 2606:4700:20::ac43:48da
The subdomain shop.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for shop.com.com.
Non-responsive IP for store.com.com: 2606:4700:20::681a:494
The subdomain store.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for store.com.com.
Non-responsive IP for store.com.com: 2606:4700:20::681a:594
The subdomain store.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for store.com.com.
Non-responsive IP for store.com.com: 2606:4700:20::ac43:48da
The subdomain store.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for store.com.com.
Non-responsive IP for support.com.com: 2606:4700:20::681a:494
The subdomain support.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for support.com.com.
Non-responsive IP for support.com.com: 2606:4700:20::ac43:48da
The subdomain support.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for support.com.com.
Non-responsive IP for support.com.com: 2606:4700:20::681a:594
The subdomain support.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for support.com.com.
Non-responsive IP for help.com.com: 2606:4700:20::ac43:48da
The subdomain help.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for help.com.com.
Non-responsive IP for help.com.com: 2606:4700:20::681a:594
The subdomain help.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for help.com.com.
Non-responsive IP for help.com.com: 2606:4700:20::681a:494
The subdomain help.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for help.com.com.
Non-responsive IP for docs.com.com: 2606:4700:20::681a:594
The subdomain docs.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for docs.com.com.
Non-responsive IP for docs.com.com: 2606:4700:20::ac43:48da
The subdomain docs.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for docs.com.com.
Non-responsive IP for docs.com.com: 2606:4700:20::681a:494
The subdomain docs.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for docs.com.com.
Non-responsive IP for status.com.com: 2606:4700:20::681a:494
The subdomain status.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for status.com.com.
Non-responsive IP for status.com.com: 2606:4700:20::ac43:48da
The subdomain status.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for status.com.com.
Non-responsive IP for status.com.com: 2606:4700:20::681a:594
The subdomain status.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for status.com.com.
Non-responsive IP for git.com.com: 2606:4700:20::681a:594
The subdomain git.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for git.com.com.
Non-responsive IP for git.com.com: 2606:4700:20::681a:494
The subdomain git.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for git.com.com.
Non-responsive IP for git.com.com: 2606:4700:20::ac43:48da
The subdomain git.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for git.com.com.
Non-responsive IP for ci.com.com: 2606:4700:20::ac43:48da
The subdomain ci.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for ci.com.com.
Non-responsive IP for ci.com.com: 2606:4700:20::681a:594
The subdomain ci.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for ci.com.com.
Non-responsive IP for ci.com.com: 2606:4700:20::681a:494
The subdomain ci.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for ci.com.com.
Non-responsive IP for jenkins.com.com: 2606:4700:20::681a:494
The subdomain jenkins.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for jenkins.com.com.
Non-responsive IP for jenkins.com.com: 2606:4700:20::ac43:48da
The subdomain jenkins.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for jenkins.com.com.
Non-responsive IP for jenkins.com.com: 2606:4700:20::681a:594
The subdomain jenkins.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for jenkins.com.com.
Non-responsive IP for grafana.com.com: 2606:4700:20::681a:494
The subdomain grafana.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for grafana.com.com.
Non-responsive IP for grafana.com.com: 2606:4700:20::ac43:48da
The subdomain grafana.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for grafana.com.com.
Non-responsive IP for grafana.com.com: 2606:4700:20::681a:594
The subdomain grafana.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for grafana.com.com.
Non-responsive IP for prometheus.com.com: 2606:4700:20::ac43:48da
The subdomain prometheus.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for prometheus.com.com.
Non-responsive IP for prometheus.com.com: 2606:4700:20::681a:594
The subdomain prometheus.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for prometheus.com.com.
Non-responsive IP for prometheus.com.com: 2606:4700:20::681a:494
The subdomain prometheus.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for prometheus.com.com.
Non-responsive IP for kibana.com.com: 2606:4700:20::681a:494
The subdomain kibana.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for kibana.com.com.
Non-responsive IP for kibana.com.com: 2606:4700:20::ac43:48da
The subdomain kibana.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for kibana.com.com.
Non-responsive IP for kibana.com.com: 2606:4700:20::681a:594
The subdomain kibana.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for kibana.com.com.
Non-responsive IP for elastic.com.com: 2606:4700:20::681a:594
The subdomain elastic.com.com resolves to 2606:4700:20::681a:594 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:594 is operational or remove the DNS record for elastic.com.com.
Non-responsive IP for elastic.com.com: 2606:4700:20::681a:494
The subdomain elastic.com.com resolves to 2606:4700:20::681a:494 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:494 is operational or remove the DNS record for elastic.com.com.
Non-responsive IP for elastic.com.com: 2606:4700:20::ac43:48da
The subdomain elastic.com.com resolves to 2606:4700:20::ac43:48da which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:48da is operational or remove the DNS record for elastic.com.com.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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 com.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 com.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.com.com, resolving to 104.26.4.148, 104.26.5.148, 172.67.72.218. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.com.com is active and requires authentication.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
192.185.4.29 (gator4018.hostgator.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on all.s5h.net
192.185.4.29 (gator4018.hostgator.com) is listed on blacklist all.s5h.net (response: 127.0.0.2).
💡 Visit the all.s5h.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
192.185.4.29 (gator4018.hostgator.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing Strict-Transport-Security on com.com
The Strict-Transport-Security header is not set on https://com.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Wildcard MX records detected
Domain com.com has wildcard MX records, which can be abused for spam or phishing.
💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.
HSTS enabled with preload on webmail.com.com
Strict-Transport-Security: max-age=106384710; includeSubDomains; preload
security.txt present
Found security.txt at https://com.com/.well-known/security.txt.
TLS certificate valid for 58 days
Certificate for com.com expires on 2026-07-27.
Certificate issued by WE1
The certificate for com.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for com.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for com.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for com.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on com.com.
Domain valid for 318 days
Domain com.com expires on 2027-04-14.
Domain transfer and delete locks enabled
Domain com.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for com.com do not match known disposable email provider patterns.
Domain is 11370 days old
Domain com.com was registered 1995-04-13.
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 (gator4018.hostgator.com) uses with cipher including Forward Secrecy.
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: GoDaddy.com, LLC | Created: 1995-04-13 | Expires: 2027-04-14 | Updated: 2026-04-07
WHOIS privacy protection enabled
Domain com.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: om.com (has MX!), cm.com (has MX!), co.com (has MX!), cmo.com (has MX!), dom.com (has MX!)
22 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 22. 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 configured
→
DMARC Policy
DMARC policy missing
⚠️ DMARC policy is missing. Even with DKIM configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
Mail Server Identity: gator4018.hostgator.com
PTR record proves mail server legitimacy
MX: gator4018.hostgator.com
Mail server at 192.185.4.29
→
PTR Record
Reverse DNS: gator4018.hostgator.com
Mail Server Reputation: gator4018.hostgator.com
RBL check ensures server is not blacklisted
MX: gator4018.hostgator.com
Mail server at 192.185.4.29
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS failure reporting configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/com.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan com.com Again