piratenpartei.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
✗Problems found
23 passed 6 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a ip4:144.76.184.118 ip6:2a01:4f8:1c1a:3592::1 mx a:redmine.piratenpartei.de include:spf.crsend.com mx ip4:94.130.56.131/32 ip6:2a01:4f8:c0c:7de7::1/64 ip4:85.10.193.181 ip6:2a01:4f8:a0:61fe::2 -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=quarantine;adkim=r;aspf=r
Found at
_dmarc.piratenpartei.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF 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

pass

Selectors: dkim

Found

Selectors
dkim
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 2048 bits

Checks

  • ✓ Keys found: dkim #7
    DKIM keys found for this domain with selectors: dkim
  • ✓ Strong keys #23
    DKIM keys are strong enough: dkim: RSA 2048 bits.
  • ✓ 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

1 mail server

Found

PriorityHostRecordsReverse DNS
0mailcow.piratenpartei.deA 144.76.184.118 AAAA 2a01:4f8:200:624c::2mailcow.piratenpartei.de ✓ mailcow.piratenpartei.de ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 2 MX addresss have a PTR record that resolves back to them.

TLS

fail

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mailcow.piratenpartei.de3 1 1 d089e44082bf7b91…No

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
  • ✗
    TLSA records not DNSSEC-validated
    These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mailcow.piratenpartei.de.
    #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