paulgraham.com

Checked 22 October 2026, 10:12 UTC · via 8.8.8.8
✗Problems found
19 passed 6 warnings 1 failed 5 info

Registration

fail

.com generic · easyDNS Technologies Inc. · expires 2027-10-28

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
easyDNS Technologies Inc.
Registered
29 October 1998
Last changed
13 October 2026
Expires
28 October 2027
Status
client transfer prohibited, client update prohibited
Registry nameservers
yns1.yahoo.com, yns2.yahoo.com
RDAP server
https://rdap.verisign.com/com/v1/
Lookup error: DNS query for com failed: read udp 46.225.38.91:50398->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The TLD lookup failed, so this could not be checked: DNS query for com failed: read udp 46.225.38.91:50398->8.8.8.8:53: i/o timeout
    #1
  • ✗
    TLD not in the root zone
    .com is not delegated in the root zone, so names under it can't be resolved on the public internet.
    #2
  • ✓ Expires on 2027-10-28 #3
    The registration is valid until 2027-10-28 (370 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

yns1.yahoo.com, yns2.yahoo.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
yns1.yahoo.com, yns2.yahoo.com
NS in the zone
ns1.turbify.com, ns2.turbify.com
NameserverAddressesNetwork (AS)Glue
ns1.turbify.com (zone only)20.121.230.119AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2.turbify.com (zone only)134.33.240.61AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
yns1.yahoo.com (parent only)34.195.51.6 34.227.186.2AS14618 AMAZON-AES - Amazon.com, Inc., US AS14618 AMAZON-AES - Amazon.com, Inc., US34.195.51.6 34.227.186.2
yns2.yahoo.com (parent only)52.3.46.62 52.73.255.93AS16509 AMAZON-02 - Amazon.com, Inc., US AS14618 AMAZON-AES - Amazon.com, Inc., US52.3.46.62 52.73.255.93

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: yns1.yahoo.com, yns2.yahoo.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: yns1.yahoo.com, yns2.yahoo.com; only in the zone: ns1.turbify.com, ns2.turbify.com. ns1.turbify.com, ns2.turbify.com, yns1.yahoo.com, yns2.yahoo.com report NS ns1.turbify.com ns2.turbify.com.
    #7
  • ✓ 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 6 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS14618 (AMAZON-AES - Amazon.com, Inc., US): 3 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 1 address; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 2 addresses.
  • 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

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.turbify.com 20.121.230.119NOERROR, 97 ms, authoritativenoyes / yesrefused-
ns2.turbify.com 134.33.240.61NOERROR, 96 ms, authoritativenoyes / yesrefused-
yns1.yahoo.com 34.195.51.6NOERROR, 99 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
yns1.yahoo.com 34.227.186.2NOERROR, 115 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
yns2.yahoo.com 52.3.46.62NOERROR, 99 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
yns2.yahoo.com 52.73.255.93NOERROR, 101 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)

Checks

  • ✓ All respond #14
    All 6 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: yns1.yahoo.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)"; yns2.yahoo.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)". 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 2026041501 · primary ns1.turbify.com

Found

Primary (MNAME)
ns1.turbify.com
Contact (RNAME)
hostmaster.paulgraham.com
Serial
2026041501
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.turbify.com (20.121.230.119)2026041501
ns2.turbify.com (134.33.240.61)2026041501
yns1.yahoo.com (34.195.51.6)2023042105
yns1.yahoo.com (34.227.186.2)2023042105
yns2.yahoo.com (52.3.46.62)2023042105
yns2.yahoo.com (52.73.255.93)2023042105

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2023042105 on yns1.yahoo.com (34.195.51.6), yns1.yahoo.com (34.227.186.2), yns2.yahoo.com (52.3.46.62), yns2.yahoo.com (52.73.255.93); 2026041501 on ns1.turbify.com (20.121.230.119), ns2.turbify.com (134.33.240.61). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.turbify.com is one of the listed nameservers.
  • ✓ Contact hostmaster@paulgraham.com #25
    The SOA RNAME hostmaster.paulgraham.com means hostmaster@paulgraham.com.
  • ✓ Date-based serial #26
    The serial 2026041501 follows the YYYYMMDDnn convention (2026-04-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

6 records at the apex

Found

Read from
20.121.230.119:53
TypeValueTTL
SOAns1.turbify.com. hostmaster.paulgraham.com. 2026041501 10800 3600 604800 36003600
NSns1.turbify.com.3599
NSns2.turbify.com.3599
A20.124.79.179120
MX10 milter1.store.yahoo.com.120
MX10 milter2.store.yahoo.com.120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 59m59s; 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