SurfaceMap › i › internet.com

internet.com

Checked 2026-10-22 09:21 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

fail

22 passed 3 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns1.name-services.com (64.98.148.137): read tcp 46.225.38.91:33282->64.98.148.137:53: i/o timeout; dns1.name-services.com (2604:4000:2800:2000:64:98:148:137): read tcp [2a01:4f8:1c1c:eebf::1]:52246->[2604:4000:2800:2000:64:98:148:137]:53: i/o timeout; dns2.name-services.com (216.40.47.201): read tcp 46.225.38.91:45982->216.40.47.201:53: i/o timeout; dns2.name-services.com (2604:4000:0:d:216:40:47:201): read tcp [2a01:4f8:1c1c:eebf::1]:58876->[2604:4000:0:d:216:40:47:201]:53: i/o timeout; dns3.name-services.com (64.98.148.138): read tcp 46.225.38.91:57096->64.98.148.138:53: i/o timeout; dns4.name-services.com (216.40.47.202): read tcp 46.225.38.91:53362->216.40.47.202:53: i/o timeout; dns4.name-services.com (2604:4000:0:d:216:40:47:202): read tcp [2a01:4f8:1c1c:eebf::1]:35256->[2604:4000:0:d:216:40:47:202]:53: i/o timeout; dns5.name-services.com (64.98.148.139): read tcp 46.225.38.91:48460->64.98.148.139:53: i/o timeout; dns5.name-services.com (2604:4000:2800:2000:64:98:148:139): read tcp [2a01:4f8:1c1c:eebf::1]:34746->[2604:4000:2800:2000:64:98:148:139]:53: i/o timeout.
    #19
  • !
    Unusual SOA timers
    SOA · refresh 2d is outside 20m–1d. Current values: refresh 2d, retry 15m, expire 21d, negative TTL 5m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: NS (0s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 0s; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for internet.com ›

Mail

warn

23 passed 6 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.internet.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:admin@cdns.net (needs internet.com._report._dmarc.cdns.net). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for internet.com ›