sfgate.com

Checked 22 October 2026, 10:41 UTC · via 8.8.8.8
!Passed with warnings
23 passed 4 warnings 0 failed 4 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-03-30

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
29 March 1994
Last changed
26 March 2026
Expires
30 March 2027
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.hearstnp.com, ns2.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns5.hearstnp.com, ns6.hearstnp.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 2027-03-30 #3
    The registration is valid until 2027-03-30 (158 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.hearstnp.com, ns2.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns5.hearstnp.com, ns6.hearstnp.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.hearstnp.com, ns2.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns5.hearstnp.com, ns6.hearstnp.com
NS in the zone
ns1.hearstnp.com, ns2.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns5.hearstnp.com, ns6.hearstnp.com
NameserverAddressesNetwork (AS)Glue
ns1.hearstnp.com34.198.18.191AS16509 AMAZON-02 - Amazon.com, Inc., US98.129.228.70
ns2.hearstnp.com34.192.165.114AS14618 AMAZON-AES - Amazon.com, Inc., US98.129.228.71
ns3.hearstnp.com34.198.18.191AS16509 AMAZON-02 - Amazon.com, Inc., US34.198.18.191
ns4.hearstnp.com34.192.165.114AS14618 AMAZON-AES - Amazon.com, Inc., US34.192.165.114
ns5.hearstnp.com52.36.105.169AS16509 AMAZON-02 - Amazon.com, Inc., US52.36.105.169
ns6.hearstnp.com34.217.162.58AS16509 AMAZON-02 - Amazon.com, Inc., US34.217.162.58

Checks

  • ✓ 6 nameservers #6
    Delegated to ns1.hearstnp.com, ns2.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns5.hearstnp.com, ns6.hearstnp.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.hearstnp.com (glue 98.129.228.70, zone 34.198.18.191); ns2.hearstnp.com (glue 98.129.228.71, zone 34.192.165.114). Update the glue at your registrar.
    #8
  • ✓ 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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14618 (AMAZON-AES - Amazon.com, Inc., US): 2 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 4 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.hearstnp.com 34.198.18.191NOERROR, 98 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu
ns2.hearstnp.com 34.192.165.114NOERROR, 98 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu
ns3.hearstnp.com 34.198.18.191NOERROR, 98 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu
ns4.hearstnp.com 34.192.165.114NOERROR, 97 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu
ns5.hearstnp.com 52.36.105.169NOERROR, 166 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu
ns6.hearstnp.com 34.217.162.58NOERROR, 172 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.24.04.8-Ubuntu

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: ns1.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns2.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns3.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns4.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns5.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; ns6.hearstnp.com: "9.18.39-0ubuntu0.24.04.8-Ubuntu". 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

pass

serial 1789063690 · primary ns1.hearstnp.com

Found

Primary (MNAME)
ns1.hearstnp.com
Contact (RNAME)
domains.hearstnp.com
Serial
1789063690
Refresh / retry
86400 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.hearstnp.com (34.198.18.191)1789063690
ns2.hearstnp.com (34.192.165.114)1789063690
ns3.hearstnp.com (34.198.18.191)1789063690
ns4.hearstnp.com (34.192.165.114)1789063690
ns5.hearstnp.com (52.36.105.169)1789063690
ns6.hearstnp.com (34.217.162.58)1789063690

Checks

  • ✓ Serial 1789063690 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.hearstnp.com is one of the listed nameservers.
  • ✓ Contact domains@hearstnp.com #25
    The SOA RNAME domains.hearstnp.com means domains@hearstnp.com.
  • ✓ Timestamp serial #26
    The serial 1789063690 is a Unix timestamp (2026-09-10 18:08 UTC).

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

info

47 records at the apex

Found

Read from
34.198.18.191:53
TypeValueTTL
SOAns1.hearstnp.com. domains.hearstnp.com. 1789063690 86400 300 2419200 300900
NSns3.hearstnp.com.86400
NSns5.hearstnp.com.86400
NSns2.hearstnp.com.86400
NSns6.hearstnp.com.86400
NSns1.hearstnp.com.86400
NSns4.hearstnp.com.86400
A34.235.224.231300
A34.204.119.243300
A34.197.233.251300
A34.198.86.45300
MX10 sfgate-com.mail.protection.outlook.com.3600
TXT"google-site-verification=cRfr3E17Tp0pgpjtWiPX1MjKaT0FqSlJRIMKM4tx-CY"3600
TXT"atlassian-domain-verification=FpL/aWW65m3p2lAjgu9uaxMnORyl2KLKjkSbpFUulvCwkkhAoyMCv0fc30dxJ7Hh"3600
TXT"google-site-verification=w7_0lPEuKP1XgagexUQY1nv5W1r-WDz7Fza0qG_8Kfo"3600
TXT"BSI103498586397"3600
TXT"google-site-verification=MhIxpkTaMNCW3TCfkC0j38khn03PtCoswQPB_DcI7qc"3600
TXT"adobe-idp-site-verification=3ebb0754e0941b0fd3e9cfe346802f5b6321a2a9bce74d7ffbcee597a1bbd8a3"3600
TXT"google-site-verification=VLzJOl3igqWf1RlOXE0CY9J8ys4uqD2hJNSFmwEDQ3g"3600
TXT"MS=ms47985603"3600
TXT"google-site-verification=L7_nw8jNjw9qsiKf7VJo9OuzFdhTZfYNibY0d3xxun8"3600
TXT"google-site-verification=3fMDP6-72ihF6y45oawiomCNZWKeQo36ocuXIvH2FSE"3600
TXT"yahoo-verification-key=g+WhEe4N0CrrEDRyZ1wwuE9mLEFvkYz2e0qq3oLPjHc="3600
TXT"680c5ce09e3441c69047611efe4faeb7"3600
TXT"google-site-verification=K8tV1DbrPFdrO7ZPariBk0n-raEK-2whiujM2STd5rU"3600
TXT"google-site-verification=1m5nOKgH4m5Nr2d1puoZgEp6cXnnKahXaLGLJwAwTA0"3600
TXT"google-site-verification=yAIpULotH9YMiQPmbN4KeEn6F-eJX1wPsJ57vurqOd0"3600
TXT"anthropic-domain-verification-qjbz25=PFuJW5qjxIuYPpxotDHWZ6Bhq"3600
TXT"cursor-domain-verification-pjkxgd=6Bn9y7uJ8Vw692k7Fno6CSwzb"3600
TXT"google-site-verification=9BCpCvbmNpBr1tKyNPPpDYON0uX28sqBX2Y93f3PTDY"3600
TXT"openai-domain-verification=dv-W45nYtCHsBlkQWvpBLfy9OiI"3600
TXT"google-site-verification=UMxOQT0gt8TERCOyRWSPP80_vMGW40-meE0Jfr8BpZM"3600
TXT"facebook-domain-verification=faosxzy5p51wicr5ie59vp2oqhidww"3600
TXT"google-site-verification=4BHoHtfYiaiDIinXeTswr4hUe2iRFYNXOHK6rj_faPo"3600
TXT"google-site-verification=s4Ck77cuaN02hprkSoPAB4mkVaPHKWHTMDoSQgfGR0A"3600
TXT"google-site-verification=36dbrWLhz5VLUFXySCsb9XVTTydxajQK4WZY7xZTzPg"3600
TXT"google-site-verification=gIbCFh-MvYslYYD0cihA67zBu6kynkGrA05QPYqjlsU"3600
TXT"google-site-verification=cPLhqvYeHN7wkiLSV6Pjoa_PY6yaKR1fWW6vKPdlrsQ"3600
TXT"v=spf1 ip4:98.129.228.67 ip4:34.239.169.101 include:spf.protection.outlook.com include:_netblocks.google.com ip4:40.121.143.48 ip4:205.220.176.159 ip4:205.220.164.154 ~all"3600
TXT"facebook-domain-verification=qqynxm212f5lyr5u525q554vlwn7kk"3600
TXT"google-site-verification=Jcpz_cHqgnfl6x94Lm_joJ9J5q6EqkiMDffkIZMbrlI"3600
TXT"google-site-verification=cVLyuJzCwJrtt7fPi8NMCEUcWPaI720_yjTazOfL7CQ"3600
TXT"_globalsign-domain-verification=Iiihy-iv_vLdlIMtHvh-aCdqO2T53oCoknhW44njXn"3600
TXT"google-site-verification=xzugS3_GIqJIfzZ1bnQ05Rj8KqdcL57WvR_5qMgI1P4"3600
TXT"google-site-verification=xE9mZkrxGdPtiY0MvoyWLhKLP4_4KqMvAvVdOPj9HGE"3600
TXT"FBFlR0fdrg02SII+qegeKCtLvJESGEhjOsY0IJlgbepKR6+ByiyyTqeAXH4CZh/qQfeWnLuDTrJg4l4lLJHE5g=="3600
TXT"tollbit-domain-verification=912537cb66cea7a2430691de74df257bf291fb9fb270a9020f16bb5fee6ec2d6"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, 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.
  • 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