SurfaceMap › b › bjcxzlfw.com

bjcxzlfw.com

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

Domain & DNS

fail

20 passed 3 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.363.hk (240e:d9:c200::2): read udp [2a01:4f8:1c1c:eebf::1]:50836->[240e:d9:c200::2]:53: i/o timeout; ns2.363.hk (61.172.183.73): read udp 46.225.38.91:44798->61.172.183.73:53: i/o timeout; ns6.363.hk (118.123.253.132): read udp 46.225.38.91:49051->118.123.253.132: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: ns1.363.hk (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns2.363.hk (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.363.hk (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns3.363.hk (61.172.183.77): dial tcp 61.172.183.77:53: i/o timeout; ns3.363.hk (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns3.363.hk (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns4.363.hk (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns4.363.hk (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns5.363.hk (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns5.363.hk (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns5.363.hk (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns6.363.hk (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.363.hk: "v1.1"; ns2.363.hk: "v1.1"; ns3.363.hk: "v1.1"; ns4.363.hk: "v1.1"; ns5.363.hk: "v1.1"; ns6.363.hk: "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: ns3.363.hk (61.172.183.77), ns5.363.hk (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 bjcxzlfw.com ›

Mail

fail

0 passed 3 warn 2 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 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
  • !
    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 bjcxzlfw.com ›