pinakothek.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
✗Problems found
18 passed 2 warnings 2 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:194.94.155.233 a mx include:_spf.mail.lrz.de include:spf.protection.outlook.com ip4:192.68.211.28 ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

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

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.pinakothek.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (3)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
49816, 20659, 53740
Signatures valid until
20 November 2026, 15:16 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-11-20 #21
    DNSKEY signatures are valid until 2026-11-20T15:16:00Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0pinakothek-de.mail.protection.outlook.comA 52.101.68.21 A 52.101.68.15 A 52.101.73.153 A 52.101.103.143 AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca04::e AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca21::email-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-as8pr05cu00401.inbound.protection.outlook.com ✓ mail-miypr03cu00107.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-matpr04cu00306.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
pinakothek-de.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