fressnapf.de

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

SPF

warn

SPF record published

Found

Record
v=spf1 ptr ip4:195.14.237.130 ip4:91.208.38.0/24 ip4:213.168.124.165 ip4:81.173.193.132 ip4:81.173.193.131 ip4:213.23.104.70 ip4:91.220.162.58 ip6:2001:4dd0:100:1020:25:a2b:0:1 ip6:2001:4dd0:100:1020:25:a2b:0:2 ip4:46.232.228.79 include:spf.protection.outlook.com include:_spf.fnmz.org ~all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

  • !
    Uses deprecated ptr mechanism
    The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • ✓ 3 of 10 DNS lookups #2
    SPF record needs 3 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.fressnapf.de)

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc@fressnapf.com; ruf=mailto:dmarc@fressnapf.com; fo=1
Found at
_dmarc.fressnapf.de
External report address
mailto:dmarc@fressnapf.com (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc@fressnapf.comAggregate report addresses
rufmailto:dmarc@fressnapf.comFailure report addresses
fo1Failure reporting options

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:dmarc@fressnapf.com
  • !
    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:dmarc@fressnapf.com (needs fressnapf.de._report._dmarc.fressnapf.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: selector1, s1

Found

Selectors
selector1, s1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
s1RSA 2048 bits

Checks

  • ✓ Keys found: selector1, s1 #7
    DKIM keys found for this domain with selectors: selector1, s1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; s1: 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
0fressnapf-de.mail.protection.outlook.comA 52.101.68.8 A 52.101.68.10 A 52.101.209.153 A 52.101.103.143 AAAA 2a01:111:f403:ca21::a AAAA 2a01:111:f403:ca04::c AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca48::amail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-miypr03cu00107.inbound.protection.outlook.com ✓ mail-maspr04cu00102.inbound.protection.outlook.com ✓ mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓

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
fressnapf-de.mail.protection.outlook.comnone-

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