paizo.com

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

Registration

fail

.com generic · GoDaddy.com, LLC · expires 2026-10-30

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
30 October 2002
Last changed
30 October 2023
Expires
30 October 2026
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1.paizo.com, ns2.paizo.com, ns3.paizo.com, ns4.paizo.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 in 8 days
    The registration expires on 2026-10-30. Renew it now or enable auto-renewal.
    #3
  • ✓ 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

info

ns1.paizo.com, ns2.paizo.com, ns3.paizo.com, ns4.paizo.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.paizo.com, ns2.paizo.com, ns3.paizo.com, ns4.paizo.com
NS in the zone
ns1.paizo.com, ns2.paizo.com, ns3.paizo.com, ns4.paizo.com
NameserverAddressesNetwork (AS)Glue
ns1.paizo.com205.251.192.208 2600:9000:5300:d000::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US2600:9000:5300:d000::1 205.251.192.208
ns2.paizo.com205.251.194.192 2600:9000:5302:c000::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.194.192 2600:9000:5302:c000::1
ns3.paizo.com205.251.197.149 2600:9000:5305:9500::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.197.149 2600:9000:5305:9500::1
ns4.paizo.com205.251.198.250 2600:9000:5306:fa00::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.198.250 2600:9000:5306:fa00::1

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.paizo.com, ns2.paizo.com, ns3.paizo.com, ns4.paizo.com.
  • ✓ 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.paizo.com, ns2.paizo.com, ns3.paizo.com, ns4.paizo.com.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16509 (AMAZON-02 - Amazon.com, Inc., US): 8 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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.paizo.com 205.251.192.208NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns1.paizo.com 2600:9000:5300:d000::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2.paizo.com 205.251.194.192NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.paizo.com 2600:9000:5302:c000::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3.paizo.com 205.251.197.149NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns3.paizo.com 2600:9000:5305:9500::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4.paizo.com 205.251.198.250NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns4.paizo.com 2600:9000:5306:fa00::1NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2019012402 · primary ns1.paizo.com

Found

Primary (MNAME)
ns1.paizo.com
Contact (RNAME)
awsdns-hostmaster.amazon.com
Serial
2019012402
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.paizo.com (205.251.192.208)2019012402
ns1.paizo.com (2600:9000:5300:d000::1)2019012402
ns2.paizo.com (205.251.194.192)2019012402
ns2.paizo.com (2600:9000:5302:c000::1)2019012402
ns3.paizo.com (205.251.197.149)2019012402
ns3.paizo.com (2600:9000:5305:9500::1)2019012402
ns4.paizo.com (205.251.198.250)2019012402
ns4.paizo.com (2600:9000:5306:fa00::1)2019012402

Checks

  • ✓ Serial 2019012402 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.paizo.com is one of the listed nameservers.
  • ✓ Contact awsdns-hostmaster@amazon.com #25
    The SOA RNAME awsdns-hostmaster.amazon.com means awsdns-hostmaster@amazon.com.
  • ✓ Date-based serial #26
    The serial 2019012402 follows the YYYYMMDDnn convention (2019-01-24).

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

12 records at the apex

Found

Read from
205.251.192.208:53
TypeValueTTL
SOAns1.paizo.com. awsdns-hostmaster.amazon.com. 2019012402 7200 900 1209600 360010800
NSns1.paizo.com.10800
NSns2.paizo.com.10800
NSns3.paizo.com.10800
NSns4.paizo.com.10800
A184.34.57.4260
A184.33.216.2160
A34.215.149.15560
MX10 inbound-smtp.us-west-2.amazonaws.com.10800
TXT"google-site-verification=ZrRcXRn9RxJG2l_zhwHlYMB9WB4oFvKrrqsy58-Pw4o"10800
TXT"klaviyo-site-verification=XaTZKm"10800
TXT"v=spf1 include:amazonses.com include:bigcommerce.net ~all"10800

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 3h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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