gruene-bundestag.de

Checked 21 October 2026, 22:41 UTC · via 8.8.8.8
✗Problems found
23 passed 5 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:94.100.132.73 ip4:94.100.136.58 ip4:159.69.170.100 ip4:31.47.234.6 ip4:5.1.92.141 ip4:116.202.31.64 ip4:193.17.243.103 ip4:193.17.232.103 ip4:159.69.170.99 -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

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

p=none (_dmarc.gruene-bundestag.de)

Found

Record
v=DMARC1;p=none;pct=100;ruf=mailto:it@gruene-bundestag.de;rua=mailto:it@gruene-bundestag.de;adkim=r;aspf=r
Found at
_dmarc.gruene-bundestag.de
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:it@gruene-bundestag.deAggregate report addresses
rufmailto:it@gruene-bundestag.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:it@gruene-bundestag.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail

Found

Selectors
mail
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits

Checks

  • ✓ Keys found: mail #7
    DKIM keys found for this domain with selectors: mail
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mail1.dbtg.deA 193.17.243.101mail1.dbtg.de ✓
20mail2.dbtg.deA 193.17.232.101mail2.dbtg.de ✓
30mail3.dbtg.deA 193.17.243.102mail3.dbtg.de ✓
40mail4.dbtg.deA 193.17.236.101mail4.dbtg.de ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mail1.dbtg.de, mail2.dbtg.de, mail3.dbtg.de, mail4.dbtg.de
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 of 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail1.dbtg.de3 1 1 e4a974c31420186f… 3 1 1 5d0fbd4152c10b28…Yes
mail2.dbtg.de3 1 1 5d0fbd4152c10b28… 3 1 1 8818a2e7d9f70535…Yes
mail3.dbtg.de3 1 1 5d0fbd4152c10b28… 3 1 1 238bfce604e61351…Yes
mail4.dbtg.de3 1 1 5d0fbd4152c10b28… 3 1 1 3db22ad186cf71fa…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 4 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