pair.com

Checked 22 October 2026, 10:11 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 6 info

Registration

info

.com generic · pair Networks, Inc. d/b/a pair Domains · expires 2027-08-17

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
pair Networks, Inc. d/b/a pair Domains
Registered
18 August 1995
Last changed
25 August 2026
Expires
17 August 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
pdns0.den.pair.net, pdns0.pit.pair.net
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-08-17 #3
    The registration is valid until 2027-08-17 (298 days).
  • ✓ Transfer locked #4
    Registry status: client delete 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

info

pdns0.den.pair.net, pdns0.pit.pair.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
pdns0.den.pair.net, pdns0.pit.pair.net
NS in the zone
pdns0.den.pair.net, pdns0.pit.pair.net
NameserverAddressesNetwork (AS)Glue
pdns0.den.pair.net216.146.198.35 2607:f441::d892:c623AS7859 PAIR-NETWORKS - pair Networks, US AS7859 PAIR-NETWORKS - pair Networks, US-
pdns0.pit.pair.net216.92.19.39 2607:f440::d85c:1327AS7859 PAIR-NETWORKS - pair Networks, US AS7859 PAIR-NETWORKS - pair Networks, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pdns0.den.pair.net, pdns0.pit.pair.net.
    #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 .net
    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
pdns0.den.pair.net 216.146.198.35NOERROR, 124 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Dec 19 2023 08:24:58 by root@localhost)
pdns0.den.pair.net 2607:f441::d892:c623NOERROR, 127 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Dec 19 2023 08:24:58 by root@localhost)
pdns0.pit.pair.net 216.92.19.39NOERROR, 94 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Dec 19 2023 08:24:58 by root@localhost)
pdns0.pit.pair.net 2607:f440::d85c:1327NOERROR, 94 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Dec 19 2023 08:24:58 by root@localhost)

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: pdns0.den.pair.net: "PowerDNS Authoritative Server 4.8.4 (built Dec 19 2023 08:24:58 by root@localhost)"; pdns0.pit.pair.net: "PowerDNS Authoritative Server 4.8.4 (built Dec 19 2023 08:24:58 by root@localhost)". 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

warn

serial 2024021518 · primary ns1.pair.com

Found

Primary (MNAME)
ns1.pair.com
Contact (RNAME)
root.pair.com
Serial
2024021518
Refresh / retry
30 s / 900 s
Expire
604800 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
pdns0.den.pair.net (216.146.198.35)2024021518
pdns0.den.pair.net (2607:f441::d892:c623)2024021518
pdns0.pit.pair.net (216.92.19.39)2024021518
pdns0.pit.pair.net (2607:f440::d85c:1327)2024021518

Checks

  • ✓ Serial 2024021518 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 30s is outside 20m–1d; retry 15m should be shorter than refresh 30s. Current values: refresh 30s, retry 15m, expire 7d, negative TTL 2h.
    #23
  • i
    Hidden master
    The primary nameserver ns1.pair.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@pair.com #25
    The SOA RNAME root.pair.com means root@pair.com.
  • ✓ Date-based serial #26
    The serial 2024021518 follows the YYYYMMDDnn convention (2024-02-15).

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

14 records at the apex

Found

Read from
216.146.198.35:53
TypeValueTTL
SOAns1.pair.com. root.pair.com. 2024021518 30 900 604800 72007200
NSpdns0.den.pair.net.7200
NSpdns0.pit.pair.net.7200
A172.67.210.11039
A104.21.34.25439
AAAA2606:4700:3035::ac43:d26e174
AAAA2606:4700:3031::6815:22fe174
MX100 mx.pair.com.300
TXT"google-site-verification=5p3cbg0QyFuBi01xFTMD8tauXHUo9Iz-6_4b0eKJUh0"300
TXT"google-site-verification=hayOo9URMjEW9WXWl0qmuSwRQigwSZGkfaZQaV64hnQ"300
TXT"BunnyTicket340650"300
TXT"google-site-verification=NHq-UmX3wzmEb3NStM3-7hqiTDZaugG6Yn_aNgaQ9KU"300
TXT"v=spf1 include:spf1.pair.com include:spf2.pair.com include:spf3.pair.com include:spf4.pair.com include:mail.zendesk.com include:spf.crowdtech.com ~all"300
TXT"google-site-verification=oGFRbz0jXuyLfeZ8DdOy-DQmjpPgQQS6TP-UZicJP8g"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (39s), AAAA (2m54s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 2h; resolvers may use either.
    #32
  • ✓ 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