htmlhelp.com

Checked 22 October 2026, 09:13 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 5 info

Registration

info

.com generic · 1API GmbH · expires 2030-06-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
1API GmbH
Registered
15 June 1996
Last changed
21 November 2025
Expires
14 June 2030
Status
client transfer prohibited
Registry nameservers
dns2.pair.com, ns0.ns0.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 2030-06-14 #3
    The registration is valid until 2030-06-14 (1330 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

dns2.pair.com, ns0.ns0.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns2.pair.com, ns0.ns0.com
NS in the zone
dns2.pair.com, ns0.ns0.com
NameserverAddressesNetwork (AS)Glue
dns2.pair.com216.146.195.24 2607:f441::d892:c318AS7859 PAIR-NETWORKS - pair Networks, US AS7859 PAIR-NETWORKS - pair Networks, US216.146.195.24 2607:f441::d892:c318
ns0.ns0.com216.92.55.21 2607:f440::d85c:3715AS7859 PAIR-NETWORKS - pair Networks, US AS7859 PAIR-NETWORKS - pair Networks, US216.92.55.21 2607:f440::d85c:3715

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns2.pair.com, ns0.ns0.com.
    #6
  • ✓ 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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS7859 (PAIR-NETWORKS - pair Networks, US): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns2.pair.com 216.146.195.24NOERROR, 124 ms, authoritativenoyes / yesrefused9.20.29
dns2.pair.com 2607:f441::d892:c318NOERROR, 128 ms, authoritativenoyes / yesrefused9.20.29
ns0.ns0.com 216.92.55.21NOERROR, 93 ms, authoritativenoyes / yesrefused9.20.29
ns0.ns0.com 2607:f440::d85c:3715NOERROR, 93 ms, authoritativenoyes / yesrefused9.20.29

Checks

  • ✓ All respond #14
    All 4 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns2.pair.com: "9.20.29"; ns0.ns0.com: "9.20.29". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026040616 · primary dns2.pair.com

Found

Primary (MNAME)
dns2.pair.com
Contact (RNAME)
root.pair.com
Serial
2026040616
Refresh / retry
3600 s / 300 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns2.pair.com (216.146.195.24)2026040616
dns2.pair.com (2607:f441::d892:c318)2026040616
ns0.ns0.com (216.92.55.21)2026040616
ns0.ns0.com (2607:f440::d85c:3715)2026040616

Checks

  • ✓ Serial 2026040616 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns2.pair.com is one of the listed nameservers.
  • ✓ Contact root@pair.com #25
    The SOA RNAME root.pair.com means root@pair.com.
  • ✓ Date-based serial #26
    The serial 2026040616 follows the YYYYMMDDnn convention (2026-04-06).

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

info

5 records at the apex

Found

Read from
216.146.195.24:53
TypeValueTTL
SOAdns2.pair.com. root.pair.com. 2026040616 3600 300 604800 36003600
NSdns2.pair.com.3600
NSns0.ns0.com.3600
A216.146.209.853600
MX50 mail1.g20.pair.com.3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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