SurfaceMap › y › yokogawa.com

yokogawa.com

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

Domain & DNS

fail

21 passed 4 warn 3 failed

Areas

iRegistration ✗Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameserver names are CNAMEs
    Delegation · Nameserver names must not be aliases (RFC 2181 10.3): zns001-kz9022.yokogawa.co.jp -> zns001-kz9021.yokogawa.co.jp.
    #9
  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: zns001-kz9021.yokogawa.co.jp (121.119.225.68): SERVFAIL, authoritative=false; zns001-kz9022.yokogawa.co.jp (121.119.225.68): SERVFAIL, authoritative=false.
    #15
  • ✗
    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: zns001-kz9021.yokogawa.co.jp (121.119.225.68): ; zns001-kz9022.yokogawa.co.jp (121.119.225.68): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: zns001-kz9022.yokogawa.co.jp. zns001-0m9001.yokogawa.co.jp, zns001-0m9002.yokogawa.co.jp, zns001-0m9006.yokogawa.co.jp report NS zns001-0m9001.yokogawa.co.jp zns001-0m9002.yokogawa.co.jp zns001-0m9006.yokogawa.co.jp zns001-kz9021.yokogawa.co.jp.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: zns001-0m9006.yokogawa.co.jp: "9.20.26". Hide or replace the version string.
    #17
  • !
    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 yokogawa.com ›

Mail

warn

23 passed 6 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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), mx (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 yokogawa.com ›