wuppertal.de

Checked 22 October 2026, 01:02 UTC · via 8.8.8.8
✗Problems found
26 passed 5 warnings 1 failed 1 info

SPF

info

SPF record published

Found

Record
v=spf1 redirect=_spf.wuppertal.de
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 DNS lookups (limit is 10).
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to _spf.wuppertal.de, whose policy applies.
    #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.wuppertal.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@stadt.wuppertal.de; adkim=r; aspf=r; sp=quarantine
Found at
_dmarc.wuppertal.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
ruamailto:dmarc@stadt.wuppertal.deAggregate report addresses
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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@stadt.wuppertal.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
9 December 2026, 12:40 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-12-09 #21
    DNSKEY signatures are valid until 2026-12-09T12:40:51Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mail1.wuppertal.deA 213.240.148.101mail1.wuppertal.de ✓
10mail2.wuppertal.deA 213.240.148.102mail2.wuppertal.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: mail1.wuppertal.de, mail2.wuppertal.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 2 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 2 of 2 MX hosts

Found

MTA-STS record
v=STSv1; id=2026061701
Policy URL
https://mta-sts.wuppertal.de/.well-known/mta-sts.txt
Policy error
https://mta-sts.wuppertal.de/.well-known/mta-sts.txt returned HTTP 403

DANE (TLSA records)

MX hostTLSADNSSEC
mail1.wuppertal.de3 0 1 f75d51fc25af4a8d… 3 0 1 fd5ad7ef7b8b95ff…Yes
mail2.wuppertal.de3 0 1 f75d51fc25af4a8d… 3 0 1 fd5ad7ef7b8b95ff…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 2026061701.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.wuppertal.de/.well-known/mta-sts.txt returned HTTP 403.
    #33
  • !
    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 2 MX hosts publish DNSSEC-validated TLSA records.

BIMI

warn

https://hcp.wuppertal.de/wuppertal-app-logo.svg

Found

Record
v=BIMI1; l=https://hcp.wuppertal.de/wuppertal-app-logo.svg
Found at
default._bimi.wuppertal.de
Logo
https://hcp.wuppertal.de/wuppertal-app-logo.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.