internet.com

Checked 22 October 2026, 09:21 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 1 failed 5 info

Registration

info

.com generic · eNom, LLC · expires 2031-05-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
7 May 1997
Last changed
3 January 2022
Expires
8 May 2031
Status
client transfer prohibited
Registry nameservers
dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2031-05-08 #3
    The registration is valid until 2031-05-08 (1658 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
NS in the zone
dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
NameserverAddressesNetwork (AS)Glue
dns1.name-services.com64.98.148.137 2604:4000:2800:2000:64:98:148:137AS32491 TUCOWS-3 - Tucows.com Co., CA AS32491 TUCOWS-3 - Tucows.com Co., CA2604:4000:2800:2000:64:98:148:137 64.98.148.137
dns2.name-services.com216.40.47.201 2604:4000:0:d:216:40:47:201AS15348 TUCOWS - Tucows.com Co., CA AS15348 TUCOWS - Tucows.com Co., CA216.40.47.201 2604:4000:0:d:216:40:47:201
dns3.name-services.com64.98.148.138 2604:4000:2800:2000:64:98:148:138AS32491 TUCOWS-3 - Tucows.com Co., CA AS32491 TUCOWS-3 - Tucows.com Co., CA2604:4000:2800:2000:64:98:148:138 64.98.148.138
dns4.name-services.com216.40.47.202 2604:4000:0:d:216:40:47:202AS15348 TUCOWS - Tucows.com Co., CA AS15348 TUCOWS - Tucows.com Co., CA216.40.47.202 2604:4000:0:d:216:40:47:202
dns5.name-services.com64.98.148.139 2604:4000:2800:2000:64:98:148:139AS32491 TUCOWS-3 - Tucows.com Co., CA AS32491 TUCOWS-3 - Tucows.com Co., CA2604:4000:2800:2000:64:98:148:139 64.98.148.139

Checks

  • ✓ 5 nameservers #6
    Delegated to dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15348 (TUCOWS - Tucows.com Co., CA): 4 addresses; AS32491 (TUCOWS-3 - Tucows.com Co., CA): 6 addresses.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.name-services.com 64.98.148.137NOERROR, 119 ms, authoritativenono / yesrefusedenom-dns
dns1.name-services.com 2604:4000:2800:2000:64:98:148:137NOERROR, 119 ms, authoritativenono / yesrefusedenom-dns
dns2.name-services.com 216.40.47.201NOERROR, 101 ms, authoritativenono / yesrefusedenom-dns
dns2.name-services.com 2604:4000:0:d:216:40:47:201NOERROR, 94 ms, authoritativenono / yesrefusedenom-dns
dns3.name-services.com 64.98.148.138NOERROR, 119 ms, authoritativenono / yesrefusedenom-dns
dns3.name-services.com 2604:4000:2800:2000:64:98:148:138NOERROR, 120 ms, authoritativenoyes / yesrefusedenom-dns
dns4.name-services.com 216.40.47.202NOERROR, 99 ms, authoritativenono / yesrefusedenom-dns
dns4.name-services.com 2604:4000:0:d:216:40:47:202NOERROR, 97 ms, authoritativenono / yesrefusedenom-dns
dns5.name-services.com 64.98.148.139NOERROR, 119 ms, authoritativenono / yesrefusedenom-dns
dns5.name-services.com 2604:4000:2800:2000:64:98:148:139NOERROR, 120 ms, authoritativenono / yesrefusedenom-dns

Checks

  • ✓ All respond #14
    All 10 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns1.name-services.com: "enom-dns"; dns2.name-services.com: "enom-dns"; dns3.name-services.com: "enom-dns"; dns4.name-services.com: "enom-dns"; dns5.name-services.com: "enom-dns".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    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
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1767014194 · primary dns1.name-services.com

Found

Primary (MNAME)
dns1.name-services.com
Contact (RNAME)
info.name-services.com
Serial
1767014194
Refresh / retry
172800 s / 900 s
Expire
1814400 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
dns1.name-services.com (64.98.148.137)1767014194
dns1.name-services.com (2604:4000:2800:2000:64:98:148:137)1767014194
dns2.name-services.com (216.40.47.201)1767014194
dns2.name-services.com (2604:4000:0:d:216:40:47:201)1767014194
dns3.name-services.com (64.98.148.138)1767014194
dns3.name-services.com (2604:4000:2800:2000:64:98:148:138)1767014194
dns4.name-services.com (216.40.47.202)1767014194
dns4.name-services.com (2604:4000:0:d:216:40:47:202)1767014194
dns5.name-services.com (64.98.148.139)1767014194
dns5.name-services.com (2604:4000:2800:2000:64:98:148:139)1767014194

Checks

  • ✓ Serial 1767014194 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 2d is outside 20m–1d. Current values: refresh 2d, retry 15m, expire 21d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.name-services.com is one of the listed nameservers.
  • ✓ Contact info@name-services.com #25
    The SOA RNAME info.name-services.com means info@name-services.com.
  • ✓ Timestamp serial #26
    The serial 1767014194 is a Unix timestamp (2025-12-29 13:16 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

warn

12 records at the apex

Found

Read from
64.98.148.137:53
TypeValueTTL
SOAdns1.name-services.com. info.name-services.com. 1767014194 172800 900 1814400 3003600
NSdns4.name-services.com.0
NSdns3.name-services.com.0
NSdns5.name-services.com.0
NSdns1.name-services.com.0
NSdns2.name-services.com.0
A51.161.130.1171800
A51.89.22.2481800
A15.204.57.671800
AAAA2001:41d0:701:1100::59d41800
MX10 mail.internet.com.1800
TXT"v=spf1 mx a:mail.cdns.net -all"1800

Checks

  • !
    Very low TTLs
    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
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35