imd-berlin.de

Checked 21 October 2026, 22:52 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:80.149.206.202 ip4:37.148.204.146 include:_spf.medicover.com include:spf.protection.outlook.com include:_spf.fireeyecloud.com include:spf.DE.exclaimer.net include:spf.de.umantis.com include:_spf.salesforce.com include:secureserver.net -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 10 of 10 DNS lookups #2
    SPF record needs 10 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.imd-berlin.de)

Found

Record
v=DMARC1; p=none; rua=mailto:postmaster@medit-service.de; ruf=mailto:postmaster@medit-service.de; fo=1
Found at
_dmarc.imd-berlin.de
External report address
mailto:postmaster@medit-service.de (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:postmaster@medit-service.deAggregate report addresses
rufmailto:postmaster@medit-service.deFailure report addresses
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:postmaster@medit-service.de
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:postmaster@medit-service.de (needs imd-berlin.de._report._dmarc.medit-service.de). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: selector1

Found

Selectors
selector1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits

Checks

  • ✓ Keys found: selector1 #7
    DKIM keys found for this domain with selectors: selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10mx.emea.email.fireeyecloud.comA 63.34.218.6 A 63.34.218.7 A 3.123.5.8 A 3.123.5.6 A 3.123.5.7 A 63.34.218.8mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx.emea.email.fireeyecloud.com
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx.emea.email.fireeyecloud.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38