ekom21.de

Checked 21 October 2026, 22:18 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:195.226.81.0/24 ip4:62.156.249.0/24 ip4:80.69.206.32/27 ip4:80.69.206.64/27 ip4:80.69.206.96/27 ip4:80.69.202.112/28 ip4:80.69.201.0/24 ip6:2a02:1010:c210:001c::/64 -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.ekom21.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@ekom21.de; ruf=mailto:dmarc@ekom21.de; fo=1; adkim=s; aspf=s
Found at
_dmarc.ekom21.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@ekom21.deAggregate report addresses
rufmailto:dmarc@ekom21.deFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

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@ekom21.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 (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
65056, 27753
Signatures valid until
29 October 2026, 00:00 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-29T00:00:00Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx3sgie.ekom21.deA 195.226.81.82 AAAA 2a02:1010:c210:2d::2bmx3sgie.ekom21.de ✓ mx3sgie.ekom21.de ✓
10mx3skas.kgrz-ks.deA 80.69.201.82mx3skas.kgrz-ks.de ✓
10mx4skas.kgrz-ks.deA 80.69.201.83mx4skas.kgrz-ks.de ✓
10mx5skas.kgrz-ks.deA 62.156.249.82mx5skas.kgrz-ks.de ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx3skas.kgrz-ks.de, mx4skas.kgrz-ks.de, mx5skas.kgrz-ks.de
    #11
  • ✓ 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.
  • ✓ Reverse DNS confirmed #30
    All 5 MX addresss have a PTR record that resolves back to them.

TLS

pass

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

Found

MTA-STS record
v=STSv1; id=175274625340Z;
Policy URL
https://mta-sts.ekom21.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mx3skas.kgrz-ks.de, mx4skas.kgrz-ks.de, mx5skas.kgrz-ks.de, mx3sgie.ekom21.de
Max age
604800 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:dmarc@ekom21.de;

DANE (TLSA records)

MX hostTLSADNSSEC
mx3sgie.ekom21.de3 1 1 9da03b927f09304f… 3 1 2 28f4354186e65a7e…Yes
mx3skas.kgrz-ks.de3 1 2 26ae2d15450c3d6e… 3 1 1 dbde190f2aa55360…Yes
mx4skas.kgrz-ks.de3 1 1 d235c7f114266624… 3 1 2 a407124e239614f1…Yes
mx5skas.kgrz-ks.de3 1 2 ef65f6582bb4e2f2… 3 1 1 456cd32ad6239448…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 175274625340Z.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 168h0m0s.
  • ✓ 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:dmarc@ekom21.de
  • ✓ DANE on all MX hosts #36
    All 4 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