SurfaceMap › s › shxqdzszy.com

shxqdzszy.com

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

Domain & DNS

fail

21 passed 3 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    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: ns1.myhostadmin.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns1.myhostadmin.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns2.myhostadmin.net (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns2.myhostadmin.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.myhostadmin.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]: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: ns1.myhostadmin.net: "v1.1"; ns2.myhostadmin.net: "v1.1". 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: ns2.myhostadmin.net (61.172.183.73).
    #20
  • !
    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

Recent checks

✗

Full report

Domain & DNS report for shxqdzszy.com ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: hzmx01.mxmail.netease.com, hzmx02.mxmail.netease.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 shxqdzszy.com ›