SurfaceMap › y › yakjk.com

yakjk.com

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

Domain & DNS

fail

20 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗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; ns3.myhostadmin.net (61.172.183.77): dial tcp 61.172.183.77:53: i/o timeout; ns3.myhostadmin.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns3.myhostadmin.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns4.myhostadmin.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns4.myhostadmin.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns5.myhostadmin.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns5.myhostadmin.net (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns5.myhostadmin.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns6.myhostadmin.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns6.myhostadmin.net. ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net report NS ns1.myhostadmin.net ns2.myhostadmin.net ns3.myhostadmin.net ns4.myhostadmin.net ns5.myhostadmin.net ns6.myhostadmin.net.
    #7
  • !
    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"; ns3.myhostadmin.net: "v1.1"; ns4.myhostadmin.net: "v1.1"; ns5.myhostadmin.net: "v1.1"; ns6.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), ns3.myhostadmin.net (61.172.183.77), ns5.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 yakjk.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.yakjk.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 yakjk.com ›