SurfaceMap › w › wxgrasp.com

wxgrasp.com

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

Domain & DNS

fail

17 passed 5 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns7.cnmsn.net (240c:4082:ffff:ff01:0:d:0:34a): read udp [2a01:4f8:1c1c:eebf::1]:50509->[240c:4082:ffff:ff01:0:d:0:34a]:53: i/o timeout; ns8.cnmsn.net (240c:4082:ffff:ff01:0:d:0:69): read udp [2a01:4f8:1c1c:eebf::1]:35989->[240c:4082:ffff:ff01:0:d:0:69]:53: i/o timeout.
    #14
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns7.cnmsn.net (61.172.183.76): dial tcp 61.172.183.76:53: i/o timeout; ns7.cnmsn.net (61.240.129.114): dial tcp 61.240.129.114:53: i/o timeout; ns8.cnmsn.net (61.240.129.147): dial tcp 61.240.129.147:53: i/o timeout; ns8.cnmsn.net (61.172.183.70): dial tcp 61.172.183.70:53: i/o timeout.
    #19
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns7.cnmsn.net: "9.11.0pre-alpha"; ns8.cnmsn.net: "9.11.0pre-alpha". Hide or replace the version string.
    #17
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns7.cnmsn.net (61.172.183.76), ns8.cnmsn.net (61.172.183.70).
    #20
  • !
    Unusual SOA timers
    SOA · expire 4h is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 4h must be longer than refresh + retry. Current values: refresh 8h, retry 4h, expire 4h, negative TTL 10m.
    #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 (2m), MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for wxgrasp.com ›

Mail

fail

7 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxbiz1.qq.com, mxbiz2.qq.com
    #11
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.86.78.3 (mxbiz1.qq.com), 103.86.78.2 (mxbiz1.qq.com), 43.154.252.16 (mxbiz2.qq.com), 43.154.252.202 (mxbiz2.qq.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 wxgrasp.com ›