panix.com

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

Registration

info

.com generic · pair Networks, Inc. d/b/a pair Domains · expires 2030-04-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
pair Networks, Inc. d/b/a pair Domains
Registered
22 April 1991
Last changed
26 June 2026
Expires
23 April 2030
Status
client transfer prohibited
Registry nameservers
ns1.access.net, ns2.access.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 2030-04-23 #3
    The registration is valid until 2030-04-23 (1278 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

warn

ns1.access.net, ns2.access.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.access.net, ns2.access.net
NS in the zone
ns1.access.net, ns2.access.net
NameserverAddressesNetwork (AS)Glue
ns1.access.net198.7.0.1 2602:f977::11AS2033 PANIX - Panix, US AS2033 PANIX - Panix, US-
ns2.access.net198.7.0.2 2602:f977::12AS2033 PANIX - Panix, US AS2033 PANIX - Panix, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.access.net, ns2.access.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 one network
    all IPv4 addresses are in 198.7.0.0/24; all IPv6 addresses are in 2602:f977::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS2033 (PANIX - Panix, 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
ns1.access.net 198.7.0.1NOERROR, 84 ms, authoritativenoyes / yesrefused9.20.24
ns1.access.net 2602:f977::11NOERROR, 109 ms, authoritativenoyes / yesrefused9.20.24
ns2.access.net 198.7.0.2NOERROR, 84 ms, authoritativenoyes / yesrefused9.20.24
ns2.access.net 2602:f977::12NOERROR, 110 ms, authoritativenoyes / yesrefused9.20.24

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: ns1.access.net: "9.20.24"; ns2.access.net: "9.20.24". 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 2026090900 · primary panix.com

Found

Primary (MNAME)
panix.com
Contact (RNAME)
hostmaster.panix.com
Serial
2026090900
Refresh / retry
300 s / 300 s
Expire
3600000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.access.net (198.7.0.1)2026090900
ns1.access.net (2602:f977::11)2026090900
ns2.access.net (198.7.0.2)2026090900
ns2.access.net (2602:f977::12)2026090900

Checks

  • ✓ Serial 2026090900 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m. Current values: refresh 5m, retry 5m, expire 1000h, negative TTL 15m.
    #23
  • i
    Hidden master
    The primary nameserver panix.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 hostmaster@panix.com #25
    The SOA RNAME hostmaster.panix.com means hostmaster@panix.com.
  • ✓ Date-based serial #26
    The serial 2026090900 follows the YYYYMMDDnn convention (2026-09-09).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
31 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
22684ECDSAP256SHA256 (13)SHA256 0A14497651E4ABB8…yes

DNSKEY in the zone

Key tagRoleAlgorithm
22684KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 22684 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-31 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-31 12:18 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

pass

13 records at the apex

Found

Read from
198.7.0.1:53
TypeValueTTL
SOApanix.com. hostmaster.panix.com. 2026090900 300 300 3600000 90086400
NSns2.access.net.86400
NSns1.access.net.86400
A166.84.62.12586400
A166.84.62.25386400
AAAA2602:f977:0:2::9186400
AAAA2602:f977:0:2::1186400
MX150 mx.panix.com.86400
TXT"v=spf1 ip4:166.84.1.64/26 ip4:166.84.1.198 ?all"86400
CAA128 issue "letsencrypt.org"86400
CAA128 issue "comodoca.com"86400
CAA0 iodef "mailto:hostmaster@panix.com"86400
CAA128 issuewild ";"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 1d, MX 1d, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, comodoca.com, none (issuance forbidden).