SurfaceMap › p › paulgraham.com

paulgraham.com

Checked 2026-10-22 10:12 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

19 passed 6 warn 1 failed 1 errors

lookups failed for tld; results are incomplete

Areas

✗Registration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    TLD not in the root zone
    Registration · .com is not delegated in the root zone, so names under it can't be resolved on the public internet.
    #2
  • !
    NS sets differ
    Delegation · 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 IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · 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
  • !
    Serials differ
    SOA · 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
  • !
    Not signed
    DNSSEC · 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
  • !
    Very low TTLs
    Records · 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

Recent checks

!

Full report

Domain & DNS report for paulgraham.com ›

Mail

fail

8 passed 4 warn 2 failed

Areas

✗SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: milter1.store.yahoo.com, milter2.store.yahoo.com
    #11
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for paulgraham.com ›