SurfaceMap › b › braunschweig.de

braunschweig.de

Checked 2026-10-21 21:54 UTC · first added 2026-10-21
!Passed with warnings Score 73 of 100

Domain & DNS

warn

20 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns2.icyteas.de (glue 217.160.113.157, 2001:8d8:580:401:217:160:113:157, zone 217.160.81.161, 2001:8d8:fe:53:217:160:81:161); ns3.icyteas.de (glue 89.146.248.122, 2a01:130:2000:118:89:146:248:122, zone 185.132.35.161, 2607:f1c0:fe:53:185:132:35:161). Update the glue at your registrar.
    #8
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026071501 on ns2.braunschweig.de (81.14.216.53); 2026101102 on ns.braunschweig.de (193.30.67.143), ns2.icyteas.de (217.160.81.161), ns2.icyteas.de (2001:8d8:fe:53:217:160:81:161), ns3.icyteas.de (185.132.35.161), ns3.icyteas.de (2607:f1c0:fe:53:185:132:35:161). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 braunschweig.de ›

Mail

warn

21 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
  • !
    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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mailin02.braunschweig.de, mailin01.braunschweig.de
    #11
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 193.30.67.146 -> 146.ip.braunschweig.de.
    #30
  • !
    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 braunschweig.de ›