wesel.de

Checked 22 October 2026, 01:00 UTC · via 8.8.8.8
✗Problems found
16 passed 8 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 a mx ptr ip4:194.77.253.0/24 ip4:194.77.250.0/24 ip4:194.77.237.0/24 ip4:217.113.45.225 ip6:2a02:ea2:c101:1::25:200 include:gipsprojekt.de include:mailout02.iacd.net ~all
DNS lookups
5 of 10
Void lookups
1 of 2
Problem
include:mailout02.iacd.net does not exist or has no records

Checks

  • !
    Uses deprecated ptr mechanism
    The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • !
    5 of 10 DNS lookups, with problems
    SPF record needs 5 DNS lookups (limit is 10). Problems found: include:mailout02.iacd.net does not exist or has no records.
    #2
  • ✓ 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.
  • !
    1 void lookup
    1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.wesel.de)

Found

Record
v=DMARC1; p=none; rua=mailto:rua@krzn.de
Found at
_dmarc.wesel.de
External report address
mailto:rua@krzn.de (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:rua@krzn.deAggregate report addresses

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:rua@krzn.de
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:rua@krzn.de (needs wesel.de._report._dmarc.krzn.de). Ask the report provider to publish the record, or check the address.
    #29

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

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
30mail-in.as-scan.deA 194.77.253.21 A 194.77.237.42filter6.as-scan.de ✓ m18050688.krzn.de ✓
50mx2.as-scan.deA 194.77.237.42 A 194.77.253.21m18050688.krzn.de ✓ filter6.as-scan.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: mail-in.as-scan.de, mx2.as-scan.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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail-in.as-scan.denone-
mx2.as-scan.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