SurfaceMap › e › eizo.de

eizo.de

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

Domain & DNS

fail

20 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]:33818->[2001:240:bb81::29:111]:53: read: connection reset by peer; ns020-v1il3tso4odiu1sn.v.d-53.jp (2001:240:bb81::29:1111): read tcp [2a01:4f8:1c1c:eebf::1]:52284->[2001:240:bb81::29:1111]:53: read: connection reset by peer; ns020-v1il3tso4odiu1sn.v.d-53.net (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:33834->[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-v1il3tso4odiu1sn.v.d-53.info, ns020-v1il3tso4odiu1sn.v.d-53.jp, ns020-v1il3tso4odiu1sn.v.d-53.net. dns-b.iij.ad.jp, dns-c.iij.ad.jp, ns020-v1il3tso4odiu1sn.v.d-53.info, ns020-v1il3tso4odiu1sn.v.d-53.jp, ns020-v1il3tso4odiu1sn.v.d-53.net report NS ns020-v1il3tso4odiu1sn.v.d-53.info ns020-v1il3tso4odiu1sn.v.d-53.jp ns020-v1il3tso4odiu1sn.v.d-53.net.
    #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 eizo.de ›

Mail

fail

17 passed 3 warn 2 failed

Areas

✓SPF ✗DMARC ✗DKIM !DNSSEC !MX !TLS 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 DKIM keys published
    DKIM · _domainkey.eizo.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 eizo.de ›