SurfaceMap › r › razerzone.com

razerzone.com

Checked 2026-10-22 10:25 UTC · first added 2026-10-21
✗Problems found Score 30 of 100

Domain & DNS

fail

19 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · 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]:50846->[2600:1800:11::1]:53: i/o timeout.
    #14
  • !
    Glue differs from the zone
    Delegation · 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
  • !
    Unusual SOA timers
    SOA · 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
  • !
    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 (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

Recent checks

✗

Full report

Domain & DNS report for razerzone.com ›

Mail

fail

19 passed 6 warn 3 failed

Areas

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

Problems

  • ✗
    15 DNS lookups, over the limit of 10
    SPF · SPF record needs 15 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:messaging-master.com does not exist or has no records.
    #2
  • ✗
    Multiple SPF records
    SPF · Found 3 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✗
    Weak DKIM key
    DKIM · RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): default (768 bits), pm (768 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (razerzone-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (razerzone-com.mail.protection.outlook.com). Ask your hosting provider to set one.
    #30
  • !
    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 razerzone.com ›