razer.com

Checked 22 October 2026, 10:25 UTC · via 8.8.8.8
✗Problems found
18 passed 4 warnings 1 failed 8 info

Registration

info

.com generic · 101domain GRS Limited · expires 2027-05-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
101domain GRS Limited
Registered
15 May 1998
Last changed
30 August 2021
Expires
14 May 2027
Status
client transfer prohibited, client update prohibited
Registry nameservers
ns0.razerzone.com, ns1.razerzone.com, ns2.razerzone.com, ns3.razerzone.com, ns4.razerzone.com, ns5.razerzone.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-05-14 #3
    The registration is valid until 2027-05-14 (203 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

ns0.razerzone.com, ns1.razerzone.com, ns2.razerzone.com, ns3.razerzone.com, ns4.razerzone.com, ns5.razerzone.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns0.razerzone.com, ns1.razerzone.com, ns2.razerzone.com, ns3.razerzone.com, ns4.razerzone.com, ns5.razerzone.com
NS in the zone
ns0.razerzone.com, ns1.razerzone.com, ns2.razerzone.com, ns3.razerzone.com, ns4.razerzone.com, ns5.razerzone.com
NameserverAddressesNetwork (AS)Glue
ns0.razerzone.com208.94.148.4 2600:1800:10::1AS16552 DIGICERT - Tiggee LLC, US AS16552 DIGICERT - Tiggee LLC, US208.94.148.4
ns1.razerzone.com208.80.124.4 2600:1800:11::1AS16552 DIGICERT - Tiggee LLC, US AS16552 DIGICERT - Tiggee LLC, US208.80.124.4
ns2.razerzone.com208.80.126.4AS16552 DIGICERT - Tiggee LLC, US208.80.126.4
ns3.razerzone.com208.80.125.4AS16552 DIGICERT - Tiggee LLC, US208.80.125.4
ns4.razerzone.com208.80.127.4AS16552 DIGICERT - Tiggee LLC, US208.80.127.4
ns5.razerzone.com208.94.149.4AS16552 DIGICERT - Tiggee LLC, US208.94.149.4

Checks

  • ✓ 6 nameservers #6
    Delegated to ns0.razerzone.com, ns1.razerzone.com, ns2.razerzone.com, ns3.razerzone.com, ns4.razerzone.com, ns5.razerzone.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: ns0.razerzone.com (glue 208.94.148.4, zone 208.94.148.4, 2600:1800:10::1); ns1.razerzone.com (glue 208.80.124.4, zone 208.80.124.4, 2600:1800:11::1). 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 6 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16552 (DIGICERT - Tiggee LLC, US): 8 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns2.razerzone.com, ns3.razerzone.com, ns4.razerzone.com, ns5.razerzone.com.
    #13

Nameservers

fail

7 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.razerzone.com 208.94.148.4NOERROR, 3 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast
ns0.razerzone.com 2600:1800:10::1NOERROR, 4 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast
ns1.razerzone.com 208.80.124.4NOERROR, 6 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast
ns1.razerzone.com 2600:1800:11::1no responsenono / no--
ns2.razerzone.com 208.80.126.4NOERROR, 3 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast
ns3.razerzone.com 208.80.125.4NOERROR, 3 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast
ns4.razerzone.com 208.80.127.4NOERROR, 6 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast
ns5.razerzone.com 208.94.149.4NOERROR, 3 ms, authoritativenoyes / yesrefusedDNS Made Easy Anycast

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.razerzone.com (2600:1800:11::1): read udp [2a01:4f8:1c1c:eebf::1]:36954->[2600:1800:11::1]:53: i/o timeout.
    #14
  • ✓ 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: ns0.razerzone.com: "DNS Made Easy Anycast"; ns1.razerzone.com: "DNS Made Easy Anycast"; ns2.razerzone.com: "DNS Made Easy Anycast"; ns3.razerzone.com: "DNS Made Easy Anycast"; ns4.razerzone.com: "DNS Made Easy Anycast"; ns5.razerzone.com: "DNS Made Easy Anycast".
    #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 2009013568 · primary ns10.dnsmadeeasy.com

Found

Primary (MNAME)
ns10.dnsmadeeasy.com
Contact (RNAME)
dns.dnsmadeeasy.com
Serial
2009013568
Refresh / retry
43200 s / 3600 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns0.razerzone.com (208.94.148.4)2009013568
ns0.razerzone.com (2600:1800:10::1)2009013568
ns1.razerzone.com (208.80.124.4)2009013568
ns2.razerzone.com (208.80.126.4)2009013568
ns3.razerzone.com (208.80.125.4)2009013568
ns4.razerzone.com (208.80.127.4)2009013568
ns5.razerzone.com (208.94.149.4)2009013568

Checks

  • ✓ Serial 2009013568 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 1h, expire 14d, negative TTL 3m.
    #23
  • i
    Hidden master
    The primary nameserver ns10.dnsmadeeasy.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact dns@dnsmadeeasy.com #25
    The SOA RNAME dns.dnsmadeeasy.com means dns@dnsmadeeasy.com.
  • ✓ Timestamp serial #26
    The serial 2009013568 is a Unix timestamp (2033-08-30 11:19 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

34 records at the apex

Found

Read from
208.94.148.4:53
TypeValueTTL
SOAns10.dnsmadeeasy.com. dns.dnsmadeeasy.com. 2009013568 43200 3600 1209600 18086400
NSns2.razerzone.com.86400
NSns5.razerzone.com.86400
NSns4.razerzone.com.86400
NSns1.razerzone.com.86400
NSns0.razerzone.com.86400
NSns3.razerzone.com.86400
A13.52.84.17060
MX1 razer-com.mail.protection.outlook.com.3600
TXT"google-site-verification=X5KQK-1loNSKBF9tEDH4CPcqmXyXYs2LME0jr4qBEyw"60
TXT"mYBrYPQzDfZ69WVEdGeVuPuH2y94VSjE0bPIDCP6kME="60
TXT"google-site-verification=YOLskVtAMKfMOuhdLFLcPyLPe6ezAna7Q8TAqn0Fv6k"60
TXT"39xmvhh3n0fhp91dmdg2kxcs7fsjyphn"60
TXT"miro-verification=0dda27b85a7201584f5060bd004b6a4ffc5f2e7a"60
TXT"brevo-code:ee608095fbd147ad065a3f13ce9d36ef"60
TXT"v=spf1 mx ip4:210.48.156.44/32 ip4:18.139.153.85/32 ip4:64.73.243.214/32 ip4:182.23.150.192/26 ip4:182.23.150.20/30 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 include:spf.protection.outlook.com ip4" ":23.21.109.212/32 ip4:23.21.109.197/32 ip4:147.160.167.0/26 include:_merchant.razer.com exists:%{i}.spf.rnmk.com include:amazonses.com include:sendgrid.net include:_spf.salesforce.com -all"60
TXT"atlassian-domain-verification=utnNg8mUS6W2iCPDU0aCKKTLo2vxzkaEecrx3ftF0pjWdjlYKBAUPNlrOu/CrF2O"60
TXT"atlassian-domain-verification=GrSU9rCbaedMZjDaGMsbtLdGoofpJXa+zvlXUmHyKfRytg+ofsqHRcMb1M2diYRi"60
TXT"atlassian-domain-verification=6lMtulNewBC0Jyahjm5tTvi0b+jKKM/pbKQmy2rSFrOpsDHaJIv3VJBL4l3Gemnu"60
TXT"adobe-idp-site-verification=496d37f9d6af200dad9b9e45eb6f61418bba74337aca23ece427733bd1a3413e"60
TXT"MS=ms17507098"60
TXT"workplace-domain-verification=b5bdea4e-224c-4e2e-8679-77423a715cad"60
TXT"google-site-verification=ZcYMM_1CculpDlgf_DphjCJoTHbKh5WFO-oJHun3SXw"60
TXT"6a87272a24975891c84d06e3dc825356f2e71ed6"60
TXT"google-site-verification=0lQjNuOZPgpYZfh75eytqNraH0clP2gV1pomi_joT5M"60
TXT"amazonses:jS1xAzja+UjBiAyLyG5YqqaWYu981kvuhx2b4YVulTg="60
TXT"facebook-domain-verification=0q401oev1o4o66afmlwzfmmdois7nt"60
TXT"AHEZC2HYZtW6VgZeVyi6+smfWATalrK7d6ryudZ9rm4="60
TXT"google-site-verification=KOoW1qHtjDwfVX2dJ1MuFydBUFYZsxZ6u78pi_cioeg"60
TXT"anthropic-domain-verification-r57gn9=CVfDKyyNalDN413xAgWwW7U9r"60
TXT"google-site-verification=24DUi6u56zUypLeDklqTGc466QuhNnuZZIjW_2xnqD0"60
TXT"35SenSVr2oqYoC4CpkC/s1Bp1QNUy8B8ouMCClKFxoFw6oKBCpWbGqQwAk4MufbLB5mMWtpRhDM1v1zZm48Ygg=="60
TXT"google-site-verification=r_a4O_8yCi3AvdiGxF-wMFh-Y97phDAJPDwHPtqke5M"60
TXT"amazonses:hpd7ZB+/DGuqOkToSyGZg3RW2yaliLXvw8+NjKg3490="60

Checks

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