bad-nauheim.de

Checked 21 October 2026, 21:34 UTC · via 8.8.8.8
!Passed with warnings
24 passed 6 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf1.ekom21.de include:_spf.nol-is.de +ip4:185.35.218.72/32 +ip4:185.35.218.66/32 +ip4:217.91.222.36/32 +ip4:85.236.55.225/32 +ip4:85.236.55.254/32 +a:mail.inworks.de -all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; rua=mailto:administrator@bad-nauheim.de; fo=1; adkim=s; aspf=s; rf=afrf; sp=none
Found at
_dmarc.bad-nauheim.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
ruamailto:administrator@bad-nauheim.deAggregate report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
rfafrfFailure report format

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:administrator@bad-nauheim.de
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ 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
51393, 53464
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

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx3sgie.ekom21.de3 1 2 28f4354186e65a7e… 3 1 1 9da03b927f09304f…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 1 456cd32ad6239448… 3 1 2 ef65f6582bb4e2f2…Yes

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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ 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