Mail domain report: paessler.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:62.146.75.210 ip4:62.146.75.212 include:sendgrid.net include:spf.protection.outlook.com include:2990530.spf10.hubspotemail.net ip4:91.250.95.71 ip4:92.51.187.64/27 ip4:83.169.51.224/27 ip4:80.237.187.32/28 ip4:91.250.74.128/27 ip4:87.230.74.128/28 ip4:91.250.95.64/26 ip4:85.25.89.0/24 include:fdspfus.freshemail.io include:fdspfeuc.freshemail.io ip4:147.160.167.0/26 ip4:52.49.201.246 ip4:52.49.235.189 ip4:23.21.109.197 ip4:23.21.109.212 ip4:88.99.206.140 ip4:40.68.36.243 include:_spf.salesforce.com ip4:195.10.208.0/26 ip6:2001:67c:2050::/48 -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 8 of 10 DNS lookups #2

SPF record needs 8 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.paessler.com)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:dmarc-aggregate@paessler.com,mailto:0b4d285c8ce1933@rep.dmarcanalyzer.com; ruf=mailto:dmarc-forensic@paessler.com,mailto:0b4d285c8ce1933@for.dmarcanalyzer.com; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; sp=quarantine
Found at: _dmarc.paessler.com
External report address: mailto:0b4d285c8ce1933@rep.dmarcanalyzer.com (authorized)
External report address: mailto:0b4d285c8ce1933@for.dmarcanalyzer.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-aggregate@paessler.com,mailto:0b4d285c8ce1933@rep.dmarcanalyzer.com	Aggregate report addresses
ruf	mailto:dmarc-forensic@paessler.com,mailto:0b4d285c8ce1933@for.dmarcanalyzer.com	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	0	Failure reporting options
rf	afrf	Failure report format
ri	86400	Report interval (seconds)

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-aggregate@paessler.com, mailto:0b4d285c8ce1933@rep.dmarcanalyzer.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: selector2, s1, s2

Found

Selectors: selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector2	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: selector2, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: selector2 (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
1	paessler-com.mail.protection.outlook.com	A 52.101.209.153 A 52.101.91.153 A 52.101.91.156 A 52.101.68.29 AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca09::22 AAAA 2a01:111:f403:ca04::10	mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-maspr04cu00104.inbound.protection.outlook.com ✓ mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.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 host	TLSA	DNSSEC
paessler-com.mail.protection.outlook.com	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