checkdomain.de

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

SPF

fail

SPF record published

Found

Record
v=spf1 include:_spf.cio.g1i.one include:mx.spf.checkdomain.de include:web1.spf.checkdomain.de include:spf.protection.outlook.com include:secure-mailgate.com include:mail.zendesk.com ip4:212.123.41.224/28 ip6:2a01:4f8:221:11cd:9734:4c26:6044:5f33 include:_spf.hostedemail.com ~all
DNS lookups
12 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    12 DNS lookups, over the limit of 10
    SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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

p=none (_dmarc.checkdomain.de)

Found

Record
v=DMARC1; p=none; sp=none;rua=mailto:dmarc@cp.wum.dogado.net,mailto:dmarc@mailinblue.com!10m;ruf=mailto:dmarc@cp.wum.dogado.net,mailto:dmarc@mailinblue.com!10m; rf=afrf; pct=100;ri=86400
Found at
_dmarc.checkdomain.de
External report address
mailto:dmarc@cp.wum.dogado.net (authorized)
External report address
mailto:dmarc@mailinblue.com!10m (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@cp.wum.dogado.net,mailto:dmarc@mailinblue.com!10mAggregate report addresses
rufmailto:dmarc@cp.wum.dogado.net,mailto:dmarc@mailinblue.com!10mFailure report addresses
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@cp.wum.dogado.net, mailto:dmarc@mailinblue.com!10m
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1

Found

Selectors
mail, selector1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits

Checks

  • ✓ Keys found: mail, selector1 #7
    DKIM keys found for this domain with selectors: mail, selector1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ 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

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10m1.checkdomain.deA 88.198.20.145 AAAA 2a01:4f8:222:2b49:5498:d60a:e248:3219mx1.checkdomain.de ✓ mx1.checkdomain.de ✓
20m2.checkdomain.deA 94.130.12.24 AAAA 2a01:4f8:10b:1067:c61b:626:b6c3:fc60mx2.checkdomain.de ✓ mx2.checkdomain.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.
  • ✓ 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.
  • ✓ Reverse DNS confirmed #30
    All 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
m1.checkdomain.denone-
m2.checkdomain.denone-

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

fail

https://bimi.group-cdn.one/checkdomain/v1/logo.svg

Found

Record
v=BIMI1; l=https://bimi.group-cdn.one/checkdomain/v1/logo.svg; a=https://bimi.group-cdn.one/checkdomain/v1/cert.pem
Found at
default._bimi.checkdomain.de
Logo
https://bimi.group-cdn.one/checkdomain/v1/logo.svg
Certificate
https://bimi.group-cdn.one/checkdomain/v1/cert.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://bimi.group-cdn.one/checkdomain/v1/logo.svg; certificate: https://bimi.group-cdn.one/checkdomain/v1/cert.pem
  • ✗
    DMARC not strict enough for BIMI
    Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.
    #39