SurfaceMap › b › bvmed.de

bvmed.de

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

Domain & DNS

warn

21 passed 2 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: pns.glamus.de (glue 46.163.89.101, zone 46.163.89.101, 2a02:cbf3:204::1b6). Update the glue at your registrar.
    #8
  • !
    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 bvmed.de ›

Mail

fail

17 passed 7 warn 1 failed

Areas

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

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
  • !
    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: owa.bvmed.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
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:e-mail-admin@glamus.de (needs bvmed.de._report._dmarc.glamus.de). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 213.138.58.130 -> L1066421.vt-security.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 bvmed.de ›