wolfsburg.de

Checked 22 October 2026, 01:01 UTC · via 8.8.8.8
!Passed with warnings
24 passed 4 warnings 0 failed 4 info

SPF

info

SPF record published

Found

Record
v=spf1 redirect=_spf.wobcom.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.wobcom.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=reject (_dmarc.wolfsburg.de)

Found

Record
v=DMARC1; p=reject; rua=mailto:dmarc@wolfsburg.de; ruf=mailto:dmarc@wolfsburg.de; fo=1; sp=none;
Found at
_dmarc.wolfsburg.de
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
ruamailto:dmarc@wolfsburg.deAggregate report addresses
rufmailto:dmarc@wolfsburg.deFailure report addresses
fo1Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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@wolfsburg.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
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

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
10mx.wobcom.deA 62.176.226.53 A 62.176.226.51 A 62.176.226.54 A 62.176.226.52 AAAA 2a01:581:2:0:1001:5ee:bad:c0de AAAA 2a01:581:2:0:1:5ee:bad:c0de AAAA 2a01:581:2:0:2001:5ee:bad:c0de AAAA 2a01:581:2:0:3001:5ee:bad:c0demail-out-3.wobcom.de ✓ mail-out-1.wobcom.de ✓ mail-out-4.wobcom.de ✓ mail-out-2.wobcom.de ✓ mail-out-2.wobcom.de ✓ mail-out-1.wobcom.de ✓ mail-out-3.wobcom.de ✓ mail-out-4.wobcom.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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx.wobcom.denone-

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