Mail domain report: knauf.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:18.141.248.4 ip4:3.125.230.255 ip4:198.245.81.0/24 ip4:136.147.176.0/24 ip4:13.111.0.0/16 ip4:157.90.94.187 ip4:212.2.69.178 ip4:82.210.238.38 ip4:82.210.238.39 ip4:136.147.182.0/24 ip4:136.147.135.0/24 ip4:199.122.123.0/24 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ip4:86.59.12.25 ip4:86.59.12.47 ip4:86.59.12.31 ip4:150.60.232.72 ip4:193.228.122.60 ip4:193.228.122.61 ip4:52.49.235.189 ip4:52.49.201.246 ip4:147.160.167.0/26 ip4:23.21.109.212 ip4:23.21.109.197 ip4:94.231.81.6 ip4:213.95.132.52 ip4:213.155.74.87 ip4:213.155.74.157 ip4:213.155.74.23 ip4:213.155.74.133 a:c.spf.service-now.com include:spf.protection.outlook.com include:ciphr247.com include:spf-mailer-knauf.aufwind-solutions.de include:sendgrid.net include:agenturserver.de exists:%{i}._spf.mta.salesforce.com include:amazonses.com include:25192585.spf02.hubspotemail.net ~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.com)

Found

Record: v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:2650734a09884a4abf36e6de219cc429@dmarc-reports.cloudflare.net,mailto:dmarc_reports@knauf.com; ruf=mailto:Forensic_dmarc_reports@knauf.com; adkim=s; aspf=s;
Found at: _dmarc.knauf.com
External report address: mailto:2650734a09884a4abf36e6de219cc429@dmarc-reports.cloudflare.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
rua	mailto:2650734a09884a4abf36e6de219cc429@dmarc-reports.cloudflare.net,mailto:dmarc_reports@knauf.com	Aggregate report addresses
ruf	mailto:Forensic_dmarc_reports@knauf.com	Failure report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF 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:2650734a09884a4abf36e6de219cc429@dmarc-reports.cloudflare.net, mailto:dmarc_reports@knauf.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1, selector2, s1, s2

Found

Selectors: mail, selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
selector1	RSA 1024 bits
selector2	RSA 1024 bits
s1	RSA 1024 bits
s2	RSA 1024 bits

Checks

✓ Keys found: mail, selector1, selector2, s1, s2 #7

DKIM keys found for this domain with selectors: mail, selector1, selector2, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), 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

Priority	Host	Records	Reverse DNS
10	mailstream-eu1.mxrecord.io	A 172.65.245.214	no 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 host	TLSA	DNSSEC
mailstream-eu1.mxrecord.io	none	-

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