fairtrade-deutschland.de

Checked 21 October 2026, 22:20 UTC · via 8.8.8.8
!Passed with warnings
22 passed 7 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:116.200.252.175 include:_spf.zimpel.de include:spf.protection.outlook.com include:_spf.salesforce.com include:antispameurope.com include:shops.shopify.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=quarantine;sp=none;pct=100;rua=mailto:a01875b109@rua.easydmarc.eu,mailto:ftd.dmarc@fairtrade-deutschland.de;ruf=mailto:a01875b109@ruf.easydmarc.eu,mailto:ftd.dmarc@fairtrade-deutschland.de;ri=86400;aspf=r;adkim=r;fo=1;
Found at
_dmarc.fairtrade-deutschland.de
External report address
mailto:a01875b109@rua.easydmarc.eu (authorized)
External report address
mailto:a01875b109@ruf.easydmarc.eu (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:a01875b109@rua.easydmarc.eu,mailto:ftd.dmarc@fairtrade-deutschland.deAggregate report addresses
rufmailto:a01875b109@ruf.easydmarc.eu,mailto:ftd.dmarc@fairtrade-deutschland.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
ri86400Report interval (seconds)

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:a01875b109@rua.easydmarc.eu, mailto:ftd.dmarc@fairtrade-deutschland.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
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2 #7
    DKIM keys found for this domain with selectors: selector1, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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
10fairtrade-deutschland-mx1.titanhq.comA 3.125.67.59 A 35.158.242.254 A 35.158.11.197 A 3.70.162.203eu1-smtp1.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp1.titanhq.com (does not resolve back)
10fairtrade-deutschland-mx2.titanhq.comA 3.125.67.59 A 35.158.11.197 A 35.158.242.254 A 3.70.162.203eu1-smtp1.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp1.titanhq.com (does not resolve back)

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: fairtrade-deutschland-mx1.titanhq.com, fairtrade-deutschland-mx2.titanhq.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 does not match
    The PTR name of these addresses does not resolve back to the same address: 3.125.67.59 -> eu1-smtp1.titanhq.com, 35.158.242.254 -> eu1-smtp2.titanhq.com, 35.158.11.197 -> eu1-smtp2.titanhq.com, 3.70.162.203 -> eu1-smtp1.titanhq.com, 3.125.67.59 -> eu1-smtp1.titanhq.com, 35.158.11.197 -> eu1-smtp2.titanhq.com, 35.158.242.254 -> eu1-smtp2.titanhq.com, 3.70.162.203 -> eu1-smtp1.titanhq.com.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
fairtrade-deutschland-mx1.titanhq.comnone-
fairtrade-deutschland-mx2.titanhq.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