kdo.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
31 passed 2 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:194.76.65.37/32 ip4:194.76.65.40/32 ip4:194.76.65.116/32 ip4:194.76.65.109/32 ip4:194.76.65.119/32 -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 #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=reject (_dmarc.kdo.de)

Found

Record
v=DMARC1;p=reject;sp=reject;rua=mailto:dmarc-report@kdo-service.de;ruf=mailto:dmarc-report@kdo-service.de;fo=1;
Found at
_dmarc.kdo.de
External report address
mailto:dmarc-report@kdo-service.de (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:dmarc-report@kdo-service.deAggregate report addresses
rufmailto:dmarc-report@kdo-service.deFailure report addresses
fo1Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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-report@kdo-service.de
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-report@kdo-service.de (needs kdo.de._report._dmarc.kdo-service.de). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: default, dkim

Found

Selectors
default, dkim
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 2048 bits
dkimRSA 2048 bits

Checks

  • ✓ Keys found: default, dkim #7
    DKIM keys found for this domain with selectors: default, dkim
  • ✓ Strong keys #23
    DKIM keys are strong enough: default: RSA 2048 bits; dkim: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
24280, 25113
Signatures valid until
31 October 2026, 15:17 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-31 #21
    DNSKEY signatures are valid until 2026-10-31T15:17:40Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mta1in.kdo.deA 194.76.65.144mta1in.kdo.de ✓
10mta2in.kdo.deA 194.76.65.145mta2in.kdo.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: mta1in.kdo.de, mta2in.kdo.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=20241008142300;
Policy URL
https://mta-sts.kdo.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mta1in.kdo.de, mta2in.kdo.de
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:int-statusmails@kdo.de

DANE (TLSA records)

MX hostTLSADNSSEC
mta1in.kdo.denone-
mta2in.kdo.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20241008142300.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 24h0m0s.
  • ✓ 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:int-statusmails@kdo.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

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