pjrc.com

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

Registration

info

.com generic · DomainSpot LLC · expires 2033-04-02

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
DomainSpot LLC
Registered
2 April 1999
Last changed
19 March 2024
Expires
2 April 2033
Status
client transfer prohibited
Registry nameservers
ns1.pjrc.com, ns2.pjrc.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 2033-04-02 #3
    The registration is valid until 2033-04-02 (2353 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.pjrc.com, ns2.pjrc.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.pjrc.com, ns2.pjrc.com
NS in the zone
ns1.pjrc.com, ns2.pjrc.com
NameserverAddressesNetwork (AS)Glue
ns1.pjrc.com162.254.150.250AS29802 HVC-AS - HIVELOCITY, Inc., US162.254.150.250
ns2.pjrc.com162.254.150.250AS29802 HVC-AS - HIVELOCITY, Inc., US162.254.150.250

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.pjrc.com, ns2.pjrc.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.pjrc.com, ns2.pjrc.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 162.254.150.0/24. 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 (AS29802 (HVC-AS - HIVELOCITY, Inc., US): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.pjrc.com 162.254.150.250NOERROR, 110 ms, authoritativenoyes / yesALLOWED (30 records)9.18.39-0ubuntu0.22.04.7-Ubuntu
ns2.pjrc.com 162.254.150.250NOERROR, 110 ms, authoritativenoyes / yesALLOWED (30 records)9.18.39-0ubuntu0.22.04.7-Ubuntu

Checks

  • ✓ All respond #14
    All 2 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.pjrc.com: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; ns2.pjrc.com: "9.18.39-0ubuntu0.22.04.7-Ubuntu". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.pjrc.com (162.254.150.250): 30 records; ns2.pjrc.com (162.254.150.250): 30 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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

info

serial 2001110313 · primary pjrc.com

Found

Primary (MNAME)
pjrc.com
Contact (RNAME)
paul.pjrc.com
Serial
2001110313
Refresh / retry
14400 s / 7200 s
Expire
3600000 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.pjrc.com (162.254.150.250)2001110313
ns2.pjrc.com (162.254.150.250)2001110313

Checks

  • ✓ Serial 2001110313 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 1000h, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver pjrc.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 paul@pjrc.com #25
    The SOA RNAME paul.pjrc.com means paul@pjrc.com.
  • ✓ Date-based serial #26
    The serial 2001110313 follows the YYYYMMDDnn convention (2001-11-03).

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

pass

8 records at the apex

Found

Read from
162.254.150.250:53
TypeValueTTL
SOApjrc.com. paul.pjrc.com. 2001110313 14400 7200 3600000 36001800
NSns1.pjrc.com.1800
NSns2.pjrc.com.1800
A162.254.150.2501800
MX10 mail.pjrc.com.1800
TXT"v=spf1 a:pjrc.com a:forum.pjrc.com a:mail.pjrc.com a:wallace.pjrc.com -all"1800
CAA0 issue "comodoca.com"1800
CAA0 issue "letsencrypt.org"1800

Checks

  • ✓ TTLs within range #32
    TTLs: A 30m, MX 30m, NS 30m. The NS TTL at the parent is 2d and in the zone 30m; 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: comodoca.com, letsencrypt.org.