SurfaceMap › k › konicaminolta.com

konicaminolta.com

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

Domain & DNS

fail

23 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers iSOA !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: dns-c.iij.ad.jp (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:51092->[2001:240:bb81::29:111]:53: read: connection reset by peer; ns020-31ong4vgembe42fr.3.d-53.jp (2001:240:bb81::29:1111): read tcp [2a01:4f8:1c1c:eebf::1]:55110->[2001:240:bb81::29:1111]:53: read: connection reset by peer; ns020-31ong4vgembe42fr.3.d-53.org (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:51094->[2001:240:bb81::29:111]:53: read: connection reset by peer.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns-b.iij.ad.jp, dns-c.iij.ad.jp; only in the zone: ns020-31ong4vgembe42fr.3.d-53.info, ns020-31ong4vgembe42fr.3.d-53.jp, ns020-31ong4vgembe42fr.3.d-53.org. dns-b.iij.ad.jp, dns-c.iij.ad.jp, ns020-31ong4vgembe42fr.3.d-53.info, ns020-31ong4vgembe42fr.3.d-53.jp, ns020-31ong4vgembe42fr.3.d-53.org report NS ns020-31ong4vgembe42fr.3.d-53.info ns020-31ong4vgembe42fr.3.d-53.jp ns020-31ong4vgembe42fr.3.d-53.org.
    #7
  • !
    Signed but not delegated securely
    DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for konicaminolta.com ›

Mail

warn

27 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Signed, but no DS at parent
    DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: gw9150.fortimail.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (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 konicaminolta.com ›