knauf.de

Checked 21 October 2026, 23:10 UTC · via 8.8.8.8
!Passed with warnings
22 passed 7 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:mail.bechtlecloud.com a:c.spf.service-now.com include:spf.protection.outlook.com include:sendgrid.net include:_spf.salesforce.com include:spf-mailer-knauf.aufwind-solutions.de include:et._spf.pardot.com include:amazonses.com ip4:31.220.120.101 ip4:18.192.112.255 ip4:82.210.238.38 ip4:82.210.238.39 ip4:212.2.66.147 ip4:157.90.94.187 ip4:185.183.157.187 ip6:2a01:488:67:1000:5bfa:511a::1 -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

warn

p=quarantine (_dmarc.knauf.de)

Found

Record
v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc_reports@knauf.com; ruf=mailto:Forensic_dmarc_reports@knauf.com; aspf=s; adkim=s;
Found at
_dmarc.knauf.de
External report address
mailto:dmarc_reports@knauf.com (authorized)
External report address
mailto:Forensic_dmarc_reports@knauf.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
sprejectSubdomain policy
ruamailto:dmarc_reports@knauf.comAggregate report addresses
rufmailto:Forensic_dmarc_reports@knauf.comFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF 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_reports@knauf.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 1024 bits
s2RSA 1024 bits

Checks

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

1 mail server

Found

PriorityHostRecordsReverse DNS
10mailstream-eu1.mxrecord.ioA 172.65.245.214no PTR

Checks

  • ✓ 1 MX record #9
    Found 1 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: mailstream-eu1.mxrecord.io
    #11
  • !
    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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 172.65.245.214 (mailstream-eu1.mxrecord.io). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mailstream-eu1.mxrecord.ionone-

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