national.com

Checked 22 October 2026, 10:00 UTC · via 8.8.8.8
✗Problems found
10 passed 3 warnings 1 failed 2 info

Registration

info

.com generic · GoDaddy.com, LLC · expires 2027-05-31

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
31 January 1996
Last changed
28 January 2026
Expires
31 May 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns.ti.com, ns2.ti.com, ns3.ti.com, ns4.ti.com, nsde.ti.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 2027-05-31 #3
    The registration is valid until 2027-05-31 (221 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns.ti.com, ns2.ti.com, ns3.ti.com, ns4.ti.com, nsde.ti.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns.ti.com, ns2.ti.com, ns3.ti.com, ns4.ti.com, nsde.ti.com
NS in the zone
ns.ti.com, ns2.ti.com, ns3.ti.com, ns4.ti.com
NameserverAddressesNetwork (AS)Glue
ns.ti.com198.47.19.1AS161 TI-AS - Texas Instruments Incorporated, US198.47.19.1
ns2.ti.com198.47.19.2AS161 TI-AS - Texas Instruments Incorporated, US198.47.19.2
ns3.ti.com198.47.26.139AS161 TI-AS - Texas Instruments Incorporated, US198.47.26.139
ns4.ti.com198.47.26.138AS161 TI-AS - Texas Instruments Incorporated, US198.47.26.138
nsde.ti.com (parent only)192.91.60.31AS12801 TID-AS - Texas Instruments Deutschland GmbH, FR192.91.60.31

Checks

  • ✓ 5 nameservers #6
    Delegated to ns.ti.com, ns2.ti.com, ns3.ti.com, ns4.ti.com, nsde.ti.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: nsde.ti.com.
    #7
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12801 (TID-AS - Texas Instruments Deutschland GmbH, FR): 1 address; AS161 (TI-AS - Texas Instruments Incorporated, US): 4 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

0 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.ti.com 198.47.19.1no responsenono / no--
ns2.ti.com 198.47.19.2no responsenono / no--
ns3.ti.com 198.47.26.139no responsenono / no--
ns4.ti.com 198.47.26.138no responsenono / no--
nsde.ti.com 192.91.60.31no responsenono / no--

Checks

  • ✗
    No nameserver responds
    None of the nameserver addresses answered: ns.ti.com (198.47.19.1): read udp 46.225.38.91:57505->198.47.19.1:53: i/o timeout; ns2.ti.com (198.47.19.2): read udp 46.225.38.91:60135->198.47.19.2:53: i/o timeout; ns3.ti.com (198.47.26.139): read udp 46.225.38.91:54254->198.47.26.139:53: i/o timeout; ns4.ti.com (198.47.26.138): read udp 46.225.38.91:48499->198.47.26.138:53: i/o timeout; nsde.ti.com (192.91.60.31): read udp 46.225.38.91:34842->192.91.60.31:53: i/o timeout.
    #14
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

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