SurfaceMap › s › sdyzskqyy.com

sdyzskqyy.com

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

Domain & DNS

fail

18 passed 4 warn 3 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns5.cnmsn.net (240c:4082:ffff:ff01:0:d:0:34a): read udp [2a01:4f8:1c1c:eebf::1]:57788->[240c:4082:ffff:ff01:0:d:0:34a]: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: ns5.cnmsn.net (61.240.129.114): dial tcp 61.240.129.114:53: i/o timeout; ns5.cnmsn.net (61.172.183.76): dial tcp 61.172.183.76:53: i/o timeout; ns6.cnmsn.net (61.240.129.147): dial tcp 61.240.129.147:53: i/o timeout; ns6.cnmsn.net (61.172.183.70): dial tcp 61.172.183.70:53: i/o timeout; ns6.cnmsn.net (240c:4082:ffff:ff01:0:d:0:69): dial tcp [240c:4082:ffff:ff01:0:d:0:69]:53: i/o timeout.
    #19
  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to txhxg02.clks02.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns5.cnmsn.net: "9.11.0pre-alpha"; ns6.cnmsn.net: "9.12.0"; ns6.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: ns5.cnmsn.net (61.172.183.76), ns6.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 1h.
    #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

Recent checks

✗

Full report

Domain & DNS report for sdyzskqyy.com ›

Mail

fail

0 passed 2 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX 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 DKIM keys published
    DKIM · _domainkey.sdyzskqyy.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for sdyzskqyy.com ›