datenschutz-berlin.de

Checked 21 October 2026, 22:12 UTC · via 8.8.8.8
✗Problems found
28 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:141.15.35.10 ip4:141.15.35.125 ip4:91.250.83.59 include:_spf.jpberlin.de include:spf.dialog-mail.com -all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; sp=reject; adkim=s; aspf=s; ruf=mailto:reporting@datenschutz-berlin.de; fo=1
Found at
_dmarc.datenschutz-berlin.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
sprejectSubdomain policy
rufmailto:reporting@datenschutz-berlin.deFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
20424
Signatures valid until
29 October 2026, 00:00 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
50mx1.verwalt-berlin.deA 141.15.34.10mx1.verwalt-berlin.de ✓
150mail2.datenschutz-berlin.deA 212.20.180.180mail2.datenschutz-berlin.de ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx1.verwalt-berlin.de, mail2.datenschutz-berlin.de
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 2 MX addresss have a PTR record that resolves back to them.

TLS

info

MTA-STS enforce · TLS-RPT · DANE on 0 of 2 MX hosts

Found

MTA-STS record
v=STSv1; id=202209051222;
Policy URL
https://mta-sts.datenschutz-berlin.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mx1.verwalt-berlin.de, mail2.datenschutz-berlin.de
Max age
15552000 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:reporting@datenschutz-berlin.de

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.verwalt-berlin.denone-
mail2.datenschutz-berlin.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 202209051222.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 4320h0m0s.
  • ✓ 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:reporting@datenschutz-berlin.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

fail

https://www.datenschutz-berlin.de/fileadmin/user_upload/images/logos/BlnBDI_BIMI.svg

Found

Record
v=BIMI1; l=https://www.datenschutz-berlin.de/fileadmin/user_upload/images/logos/BlnBDI_BIMI.svg; a=self;
Found at
default._bimi.datenschutz-berlin.de
Logo
https://www.datenschutz-berlin.de/fileadmin/user_upload/images/logos/BlnBDI_BIMI.svg
Certificate
self

Checks

  • ✗
    Invalid BIMI record
    Mail clients ignore the BIMI record because of: certificate URL "self" must use https://.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.