telefonseelsorge.de

Checked 22 October 2026, 00:40 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 2 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:83.137.169.130 ip4:83.137.168.0/21 include:mailbox.org -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

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

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

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.telefonseelsorge.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
61478
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 expire in 167h0m0s
    DNSKEY signatures expire at 2026-10-29T00:00:00Z (in 167h0m0s). Check that re-signing works.
    #21

MX

pass

3 mail servers

Found

PriorityHostRecordsReverse DNS
0mxext1.mailbox.orgA 80.241.60.212 AAAA 2001:67c:2050:104:0:1:25:1mx1.mailbox.org ✓ mx1.mailbox.org ✓
10mxext2.mailbox.orgA 80.241.60.215 AAAA 2001:67c:2050:104:0:2:25:1mx2.mailbox.org ✓ mx2.mailbox.org ✓
20mxext3.mailbox.orgA 80.241.60.216 AAAA 2001:67c:2050:104:0:3:25:1mx3.mailbox.org ✓ mx3.mailbox.org ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mxext1.mailbox.org3 1 1 4758af6f02dfb5dc… 3 1 1 996ad31d65e03f03… 3 1 1 e41cc7633029afdb…Yes
mxext2.mailbox.org3 1 1 996ad31d65e03f03… 3 1 1 e41cc7633029afdb… 3 1 1 4758af6f02dfb5dc…Yes
mxext3.mailbox.org3 1 1 996ad31d65e03f03… 3 1 1 e41cc7633029afdb… 3 1 1 4758af6f02dfb5dc…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 3 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