mail.de

Checked 21 October 2026, 23:21 UTC · via 8.8.8.8
!Passed with warnings
29 passed 3 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:62.201.172.0/27 ip4:62.201.172.32/27 ip6:2001:0868:0100:0600::/64 ip4:194.113.42.0/26 ip6:2a0f:f640::/56 ~all
DNS lookups
0 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc-rua@mail.de
Found at
_dmarc.mail.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc-rua@mail.deAggregate report addresses

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-rua@mail.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

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 (3)
DS at parent
Yes
Algorithms
RSASHA512 (10)
Key tags
30519, 5025, 55671
Signatures valid until
29 October 2026, 10:50 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-29T10:50:58Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx01.mail.deA 194.113.42.51 AAAA 2a0f:f640::51no PTR no PTR
10mx02.mail.deA 194.113.42.52 AAAA 2a0f:f640::52no PTR no PTR

Checks

  • ✓ 2 MX records #9
    Found 2 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.
  • ✓ 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 194.113.42.51 (mx01.mail.de), 2a0f:f640::51 (mx01.mail.de), 194.113.42.52 (mx02.mail.de), 2a0f:f640::52 (mx02.mail.de). Ask your hosting provider to set one.
    #30

TLS

pass

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

Found

MTA-STS record
v=STSv1; id=0000002;
Policy URL
https://mta-sts.mail.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mx01.mail.de, mx02.mail.de
Max age
2419200 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:tlsrpt@mail.de

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.mail.de3 1 1 9730904a64883fb6… 3 1 1 014b3d4296f63c9c…Yes
mx02.mail.de3 1 1 014b3d4296f63c9c… 3 1 1 9730904a64883fb6…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 0000002.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 672h0m0s.
  • ✓ 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@mail.de
  • ✓ DANE on all MX hosts #36
    All 2 MX hosts publish DNSSEC-validated TLSA records.

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