netlify.com

Checked 22 October 2026, 10:01 UTC · via 8.8.8.8
!Passed with warnings
26 passed 2 warnings 0 failed 3 info

Registration

info

.com generic · Name.com, Inc. · expires 2032-06-09

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Name.com, Inc.
Registered
9 June 2014
Last changed
14 May 2026
Expires
9 June 2032
Status
client transfer prohibited
Registry nameservers
dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.netlifydns.com, ns02.netlifydns.com, ns03.netlifydns.com, ns04.netlifydns.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 2032-06-09 #3
    The registration is valid until 2032-06-09 (2057 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

pass

dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.netlifydns.com, ns02.netlifydns.com, ns03.netlifydns.com, ns04.netlifydns.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.netlifydns.com, ns02.netlifydns.com, ns03.netlifydns.com, ns04.netlifydns.com
NS in the zone
dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.netlifydns.com, ns02.netlifydns.com, ns03.netlifydns.com, ns04.netlifydns.com
NameserverAddressesNetwork (AS)Glue
dns1.p04.nsone.net198.51.44.4 2620:4d:4000:6259:7:4:0:1AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns2.p04.nsone.net198.51.45.4 2a00:edc0:6259:7:4::2AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns3.p04.nsone.net198.51.44.68 2620:4d:4000:6259:7:4:0:3AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns4.p04.nsone.net198.51.45.68 2a00:edc0:6259:7:4::4AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
ns01.netlifydns.com45.54.30.1 2607:f740:e630::1AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US2607:f740:e630::1 45.54.30.1
ns02.netlifydns.com45.54.30.65 2607:f740:e630:4::1AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US2607:f740:e630:4::1 45.54.30.65
ns03.netlifydns.com45.54.30.129 2607:f740:e630:8::1AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US2607:f740:e630:8::1 45.54.30.129
ns04.netlifydns.com45.54.30.193 2607:f740:e630:c::1AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US2607:f740:e630:c::1 45.54.30.193

Checks

  • ✓ 8 nameservers #6
    Delegated to dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.netlifydns.com, ns02.netlifydns.com, ns03.netlifydns.com, ns04.netlifydns.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS62597 (NSONE - NSONE Inc, US): 8 addresses; AS63911 (NETACTUATE-AS-AP - NetActuate, Inc, US): 8 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

16 of 16 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.p04.nsone.net 198.51.44.4NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns1.p04.nsone.net 2620:4d:4000:6259:7:4:0:1NOERROR, 7 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns2.p04.nsone.net 198.51.45.4NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns2.p04.nsone.net 2a00:edc0:6259:7:4::2NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns3.p04.nsone.net 198.51.44.68NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns3.p04.nsone.net 2620:4d:4000:6259:7:4:0:3NOERROR, 7 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns4.p04.nsone.net 198.51.45.68NOERROR, 6 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns4.p04.nsone.net 2a00:edc0:6259:7:4::4NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns01.netlifydns.com 45.54.30.1NOERROR, 9 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns01.netlifydns.com 2607:f740:e630::1NOERROR, 159 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns02.netlifydns.com 45.54.30.65NOERROR, 9 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns02.netlifydns.com 2607:f740:e630:4::1NOERROR, 159 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns03.netlifydns.com 45.54.30.129NOERROR, 9 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns03.netlifydns.com 2607:f740:e630:8::1NOERROR, 160 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns04.netlifydns.com 45.54.30.193NOERROR, 9 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
ns04.netlifydns.com 2607:f740:e630:c::1NOERROR, 159 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9

Checks

  • ✓ All respond #14
    All 16 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns1.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns2.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns3.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns4.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; ns01.netlifydns.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns02.netlifydns.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns03.netlifydns.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns04.netlifydns.com: "19dd46e347df36b70933bf2be8023258586586a9".
    #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 1664458603 · primary dns1.p04.nsone.net

Found

Primary (MNAME)
dns1.p04.nsone.net
Contact (RNAME)
hostmaster.nsone.net
Serial
1664458603
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
dns1.p04.nsone.net (198.51.44.4)1664458603
dns1.p04.nsone.net (2620:4d:4000:6259:7:4:0:1)1664458603
dns2.p04.nsone.net (198.51.45.4)1664458603
dns2.p04.nsone.net (2a00:edc0:6259:7:4::2)1664458603
dns3.p04.nsone.net (198.51.44.68)1664458603
dns3.p04.nsone.net (2620:4d:4000:6259:7:4:0:3)1664458603
dns4.p04.nsone.net (198.51.45.68)1664458603
dns4.p04.nsone.net (2a00:edc0:6259:7:4::4)1664458603
ns01.netlifydns.com (45.54.30.1)1664458603
ns01.netlifydns.com (2607:f740:e630::1)1664458603
ns02.netlifydns.com (45.54.30.65)1664458603
ns02.netlifydns.com (2607:f740:e630:4::1)1664458603
ns03.netlifydns.com (45.54.30.129)1664458603
ns03.netlifydns.com (2607:f740:e630:8::1)1664458603
ns04.netlifydns.com (45.54.30.193)1664458603
ns04.netlifydns.com (2607:f740:e630:c::1)1664458603

Checks

  • ✓ Serial 1664458603 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.p04.nsone.net is one of the listed nameservers.
  • ✓ Contact hostmaster@nsone.net #25
    The SOA RNAME hostmaster.nsone.net means hostmaster@nsone.net.
  • ✓ Timestamp serial #26
    The serial 1664458603 is a Unix timestamp (2022-09-29 13:36 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

warn

50 records at the apex

Found

Read from
198.51.44.4:53
TypeValueTTL
SOAdns1.p04.nsone.net. hostmaster.nsone.net. 1664458603 43200 7200 1209600 3003600
NSdns1.p04.nsone.net.3600
NSdns2.p04.nsone.net.3600
NSdns3.p04.nsone.net.3600
NSdns4.p04.nsone.net.3600
NSns01.netlifydns.com.3600
NSns02.netlifydns.com.3600
NSns03.netlifydns.com.3600
NSns04.netlifydns.com.3600
A3.33.186.135300
A15.197.167.90300
AAAA2a05:d014:58f:6200::1f520
AAAA2a05:d014:58f:6200::1f620
MX5 alt1.aspmx.l.google.com.3600
MX1 aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX10 aspmx2.googlemail.com.3600
MX10 aspmx3.googlemail.com.3600
TXT"v=spf1 include:_spf.google.com include:amazonses.com include:7477936.spf06.hubspotemail.net -all"1800
TXT"google-site-verification=QJq3jDnGiG6osO6RJ84O-hwoEze6PAz8lO6xFgfYBO0"1800
TXT"google-site-verification=wYMhUQYu8qD8poMUBs5t2939EFiLwZQnzbjWKd1MU34"1800
TXT"3B1992ABDE"1800
TXT"h1-domain-verification=CKczCcu1TomJ5Jw2dixrsuWKyY66Kv5zwEHCLhydMRNbQhmp"1800
TXT"google-site-verification=7OuPqnxzGdTqIMmu4O6_UGXAyBS18OsJnmZN_85-WuQ"1800
TXT"hcp-domain-verification=253416eabde8d62ebb0942cf662d24a8833dcfe01c6a99069d487a5dd9cf0799"1800
TXT"miro-verification=518375d1204646621e56a0e29af14be2f0c4715c"1800
TXT"drift-domain-verification=e3a38bbc6796103d91cb92c4dd90b8804639590f53fd392f0cabce868084da2a"1800
TXT"wiz-domain-verification=2f8d51da2e10c15a2572601c95c47b85ed170b92b02154e33d9b041449a80646"1800
TXT"_cx0tigevvwdrdef0r98rdaaf2hvtk6z"1800
TXT"MS=ms55290772"1800
TXT"segment-site-verification=tQgMSMYZ00wjs1LdKMxuTCohG4KbwDlt"1800
TXT"cloudhealth=d5131546-fa1d-46b9-bdba-c16f54ac7e69"1800
TXT"google-site-verification=G4JqDTXMHpDyWoqIRwgw8PBqg-AncXqtdkHehcOR7kc"1800
TXT"stripe-verification=9D1C1530F1369B534DF4FBD5E59F7F001D819593D423960E10057937D35D4186"1800
TXT"linear-domain-verification=7ex7p22huwww"1800
TXT"openai-domain-verification=dv-BW9MtUvA6FaPTiNecdz6eful"1800
TXT"google-site-verification=zFZKxhW9F5SqX-7r11wMoqloxuhsIashrGHSVrRA4jw"1800
TXT"spacelift-domain-verification=9fuisfs"1800
TXT"hubspot-domain-verification=NzgyMzczZTEtNWYxYi00YTg0LThiZGItMmUxMTg4ZjI5YThl"1800
TXT"MS=ms47723390"1800
TXT"openai-domain-verification=dv-MhwcRZa075RmqeHB80JuxtuE"1800
TXT"google-site-verification=VstUa2dACr9G9eIqBIzY8OsP_QxqyzQi8Kkf_b4SEVg"1800
TXT"google-site-verification=RKT_skMbvGWA7p-t54tEBkEAfCT23V2ME1qAgv-rqI8"1800
TXT"google-site-verification=KBmq_v_BrKl2SYhxH1E37BqY5h3GaanKGaWhHDMUx7I"1800
TXT"notion-domain-verification=sb764uQHr86jHwIaCldeSpOBFHQWYBRsxCfTmgxWI5G"1800
TXT"ps-cd-verification=0762074c-74c5-46df-b787-97bfea25d218"1800
TXT"anthropic-domain-verification-w17t12=kSbLxtJwwt3y05EWJEAQUKcJo"1800
CAA128 issue "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"1800
CAA128 issue "amazon.com"1800
CAA128 iodef "mailto:security@netlify.com"1800

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1h; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, amazon.com.