messe-berlin.de

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

SPF

fail

SPF record published

Found

Record
v=spf1 ip4:80.158.28.36 a:de.umantis.com a:otc-de-spf.mms.t-systems-service.com include:spf.de.umantis.com include:_spf.pretix.eu include:spf.protection.outlook.com include:spf.haiilo.cloud include:spf.clustermail.de include:amazonses.com include:spf.mailjet.com ~all
DNS lookups
12 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    12 DNS lookups, over the limit of 10
    SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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

warn

p=quarantine (_dmarc.messe-berlin.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:monitoring@messe-berlin.net; ruf=mailto:monitoring@messe-berlin.net; fo=1; ri=86400; pct=100; adkim=r; aspf=r;
Found at
_dmarc.messe-berlin.de
External report address
mailto:monitoring@messe-berlin.net (not authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:monitoring@messe-berlin.netAggregate report addresses
rufmailto:monitoring@messe-berlin.netFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
ri86400Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:monitoring@messe-berlin.net
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • !
    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:monitoring@messe-berlin.net (needs messe-berlin.de._report._dmarc.messe-berlin.net). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ 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
0messeberlin-de01c.mail.protection.outlook.comA 52.101.170.2 A 52.101.170.0 A 52.101.170.1 A 52.101.168.0 AAAA 2a01:111:f403:ca04::f AAAA 2a01:111:f403:ca21::c AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca09::26mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-db7pr03cu00507.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.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.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 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
messeberlin-de01c.mail.protection.outlook.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