visitberlin.de

Checked 22 October 2026, 00:52 UTC · via 8.8.8.8
!Passed with warnings
29 passed 5 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:84.14.87.84 ip4:144.76.35.139 ip4:54.246.220.150 ip4:54.246.224.90 include:spf.mailjet.com include:spf.protection.outlook.com include:spf.srv2.de include:spf.rapidmail.de ~all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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

warn

p=quarantine (_dmarc.visitberlin.de)

Found

Record
v=DMARC1;p=quarantine;aspf=r;rua=mailto:dmarc@visitberlin.de
Found at
_dmarc.visitberlin.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@visitberlin.deAggregate report addresses
aspfrSPF alignment (r = relaxed, s = strict)

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:dmarc@visitberlin.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

pass

Selectors: mail, selector1

Found

Selectors
mail, selector1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bitsh=sha256
selector1RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1 #7
    DKIM keys found for this domain with selectors: mail, selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: mail: RSA 2048 bits; 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
0visitberlin-de.mail.protection.outlook.comA 52.101.185.24 A 52.101.91.162 A 52.101.209.153 A 52.101.91.21 AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:c967::c AAAA 2a01:111:f403:ca09::20 AAAA 2a01:111:f403:ca48::amail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-cpjpr05cu00204.inbound.protection.outlook.com ✓ mail-as8pr05cu00400.inbound.protection.outlook.com ✓ mail-miypr02cu00202.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

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

Found

MTA-STS record
v=STSv1; id=2026090401
Policy URL
https://mta-sts.visitberlin.de/.well-known/mta-sts.txt
Mode
testing
Allowed MX
*.mail.protection.outlook.com
Max age
604800 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:tlsrpt@visitberlin.de

DANE (TLSA records)

MX hostTLSADNSSEC
visitberlin-de.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 2026090401.
  • !
    Policy in testing mode
    With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:tlsrpt@visitberlin.de
  • 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

warn

https://download.visitberlin.de/pictures/vB_Logo_BIMI.svg

Found

Record
v=BIMI1;l=https://download.visitberlin.de/pictures/vB_Logo_BIMI.svg;a=;
Found at
default._bimi.visitberlin.de
Logo
https://download.visitberlin.de/pictures/vB_Logo_BIMI.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.