eintracht.de

Checked 21 October 2026, 22:18 UTC · via 8.8.8.8
✗Problems found
19 passed 6 warnings 1 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 mx a include:_spf_eucentral1.prod.hydra.sophos.com ip4:212.83.34.183 ip4:193.158.25.236 ip4:185.248.142.160/28 ip4:193.142.41.80/28 ip4:84.200.56.54 ip4:62.80.101.4 ip4:185.88.215.53 ip4:185.88.215.132 ip4:185.88.215.134 ip4:49.13.25.136
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).
  • ✗
    No 'all' mechanism
    SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.
    #3
  • ✓ 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.eintracht.de)

Found

Record
v=DMARC1; p=quarantine; adkim=r; aspf=s;
Found at
_dmarc.eintracht.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
adkimrDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.

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
10mx-01-eu-central-1.prod.hydra.sophos.comA 63.185.46.184 A 52.57.178.187ec2-63-185-46-184.eu-central-1.compute.amazonaws.com ✓ ec2-52-57-178-187.eu-central-1.compute.amazonaws.com ✓
20mx-02-eu-central-1.prod.hydra.sophos.comA 63.185.46.184 A 52.57.178.187ec2-63-185-46-184.eu-central-1.compute.amazonaws.com ✓ ec2-52-57-178-187.eu-central-1.compute.amazonaws.com ✓

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: mx-01-eu-central-1.prod.hydra.sophos.com, mx-02-eu-central-1.prod.hydra.sophos.com
    #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 4 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
mx-01-eu-central-1.prod.hydra.sophos.comnone-
mx-02-eu-central-1.prod.hydra.sophos.comnone-

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