dawum.de

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

SPF

warn

SPF record published

Found

Record
v=spf1 include:spf.routing.net ?all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 DNS lookups (limit is 10).
  • !
    Ends with ?all (neutral)
    SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • ✓ 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

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

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx01.routing.netA 134.0.28.13 A 134.0.28.14 AAAA 2a03:2900:1:a::13 AAAA 2a03:2900:1:a::14mx01.routing.net ✓ mx01.routing.net ✓ mx01.routing.net ✓ mx01.routing.net ✓
10mx02.routing.netA 134.0.30.163 A 134.0.30.164 AAAA 2a03:2900:1:a::15 AAAA 2a03:2900:1:a::16mx02.routing.net ✓ mx02.routing.net ✓ no PTR no PTR
10mx03.routing.netA 134.0.30.165 A 134.0.30.166 A 134.0.30.167 AAAA 2a03:2900:1:a::19 AAAA 2a03:2900:1:a::18 AAAA 2a03:2900:1:a::17mx03.routing.net ✓ mx03.routing.net ✓ mx03.routing.net ✓ mx03.routing.net ✓ mx03.routing.net ✓ mx03.routing.net ✓
20mxbackup.routing.netA 194.126.196.22 A 194.126.196.21 AAAA 2a03:2902:4:1::b AAAA 2a03:2902:4:1::amxbackup2.routing.net ✓ mxbackup1.routing.net ✓ mxbackup2.routing.net (does not resolve back) mxbackup1.routing.net (does not resolve back)

Checks

  • ✓ 4 MX records #9
    Found 4 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 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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: 2a03:2900:1:a::15 (mx02.routing.net), 2a03:2900:1:a::16 (mx02.routing.net). Ask your hosting provider to set one.
    #30

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.routing.netnone-
mx02.routing.netnone-
mx03.routing.netnone-
mxbackup.routing.netnone-

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