foes.de

Checked 21 October 2026, 22:30 UTC · via 8.8.8.8
✗Problems found
16 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:spf.civilisten.io mx:smtprelay09.ispgateway.de mx:ispgateway.de ip4:134.119.228.115 ip4:134.119.228.119 ip4:134.119.228.114 ip4:134.119.228.117 ip4:134.119.228.113 ip4:134.119.228.112 ip4:134.119.228.116 ip4:134.119.228.118 ip4:213.30.239.82 -all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

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

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

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

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
0foes-de.mail.protection.outlook.comA 52.101.103.39 A 52.101.73.123 A 52.101.68.25 A 52.101.103.162 AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca38::a AAAA 2a01:111:f403:ca09::22 AAAA 2a01:111:f403:ca38::8mail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-wa4pr05cu00102.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓
100mxlb.ispgateway.deA 80.67.18.126mxlb.ispgateway.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: mxlb.ispgateway.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 9 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
foes-de.mail.protection.outlook.comnone-
mxlb.ispgateway.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

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