nintendolife.com

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

Registration

info

.com generic · Cloudflare, Inc. · expires 2033-10-29

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Cloudflare, Inc.
Registered
29 October 2005
Last changed
2 August 2024
Expires
29 October 2033
Status
client transfer prohibited
Registry nameservers
igor.ns.cloudflare.com, jill.ns.cloudflare.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 2033-10-29 #3
    The registration is valid until 2033-10-29 (2564 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

info

igor.ns.cloudflare.com, jill.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
igor.ns.cloudflare.com, jill.ns.cloudflare.com
NS in the zone
igor.ns.cloudflare.com, jill.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
igor.ns.cloudflare.com172.64.33.119 108.162.193.119 173.245.59.119 2803:f800:50::6ca2:c177 2606:4700:58::adf5:3b77 2a06:98c1:50::ac40:2177AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.193.119 172.64.33.119 173.245.59.119 2606:4700:58::adf5:3b77 2803:f800:50::6ca2:c177 2a06:98c1:50::ac40:2177
jill.ns.cloudflare.com172.64.32.122 173.245.58.122 108.162.192.122 2606:4700:50::adf5:3a7a 2803:f800:50::6ca2:c07a 2a06:98c1:50::ac40:207aAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.192.122 172.64.32.122 173.245.58.122 2606:4700:50::adf5:3a7a 2803:f800:50::6ca2:c07a 2a06:98c1:50::ac40:207a

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: igor.ns.cloudflare.com, jill.ns.cloudflare.com.
    #6
  • ✓ 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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
igor.ns.cloudflare.com 172.64.33.119NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
igor.ns.cloudflare.com 108.162.193.119NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
igor.ns.cloudflare.com 173.245.59.119NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
igor.ns.cloudflare.com 2803:f800:50::6ca2:c177NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
igor.ns.cloudflare.com 2606:4700:58::adf5:3b77NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
igor.ns.cloudflare.com 2a06:98c1:50::ac40:2177NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 172.64.32.122NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 173.245.58.122NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 108.162.192.122NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 2606:4700:50::adf5:3a7aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 2803:f800:50::6ca2:c07aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jill.ns.cloudflare.com 2a06:98c1:50::ac40:207aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: igor.ns.cloudflare.com: "2026.10.2"; jill.ns.cloudflare.com: "2026.10.2". 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 2417099149 · primary igor.ns.cloudflare.com

Found

Primary (MNAME)
igor.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2417099149
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
igor.ns.cloudflare.com (172.64.33.119)2417099149
igor.ns.cloudflare.com (108.162.193.119)2417099149
igor.ns.cloudflare.com (173.245.59.119)2417099149
igor.ns.cloudflare.com (2803:f800:50::6ca2:c177)2417099149
igor.ns.cloudflare.com (2606:4700:58::adf5:3b77)2417099149
igor.ns.cloudflare.com (2a06:98c1:50::ac40:2177)2417099149
jill.ns.cloudflare.com (172.64.32.122)2417099149
jill.ns.cloudflare.com (173.245.58.122)2417099149
jill.ns.cloudflare.com (108.162.192.122)2417099149
jill.ns.cloudflare.com (2606:4700:50::adf5:3a7a)2417099149
jill.ns.cloudflare.com (2803:f800:50::6ca2:c07a)2417099149
jill.ns.cloudflare.com (2a06:98c1:50::ac40:207a)2417099149

Checks

  • ✓ Serial 2417099149 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver igor.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2417099149 is a Unix timestamp (2046-08-05 16:25 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

21 records at the apex

Found

Read from
172.64.33.119:53
TypeValueTTL
SOAigor.ns.cloudflare.com. dns.cloudflare.com. 2417099149 10000 2400 604800 18001800
NSigor.ns.cloudflare.com.86400
NSjill.ns.cloudflare.com.86400
A104.26.7.243300
A104.26.6.243300
A172.67.69.5300
AAAA2606:4700:20::ac43:4505300
AAAA2606:4700:20::681a:7f3300
AAAA2606:4700:20::681a:6f3300
MX10 aspmx.l.google.com.300
MX20 alt1.aspmx.l.google.com.300
MX20 alt2.aspmx.l.google.com.300
MX30 aspmx2.googlemail.com.300
MX30 aspmx3.googlemail.com.300
MX30 aspmx4.googlemail.com.300
MX30 aspmx5.googlemail.com.300
TXT"brave-ledger-verification=2870c2aa4916d834202f95a819513717cdb87d80fbdc8d3fef2641f37c40bb67"300
TXT"brave-ledger-verification=5ad2ef2b0b9257ecdcb1cc7b77b8f6a19f2789f405fa155aa09088c49006c6e2"300
TXT"facebook-domain-verification=n2yjmw0npb3savib2riq213jyfc1zr"300
TXT"google-site-verification=C7tQq_lclPsH0cYBlv7NLWPB5ABSRELmhCU-jmG0iAY"300
TXT"v=spf1 a mx ip4:165.232.106.172 include:_spf.google.com include:sendgrid.net -all"300

Checks

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