SurfaceMap › d › dnb.de

dnb.de

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

Domain & DNS

fail

23 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns0.dnb.de (193.175.100.253): read udp 46.225.38.91:60151->193.175.100.253:53: i/o timeout; ns1.dnb.de (193.175.100.254): read udp 46.225.38.91:51709->193.175.100.254:53: i/o timeout.
    #14
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 1h.
    #23
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 100 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

✗

Full report

Domain & DNS report for dnb.de ›

Mail

fail

19 passed 5 warn 3 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✗
    Invalid BIMI record
    BIMI · Mail clients ignore the BIMI record because of: the record must start with v=BIMI1.
    #38
  • ✗
    DMARC not strict enough for BIMI
    BIMI · Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.
    #39
  • !
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.dnb.de
    #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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 dnb.de ›