Mail domain report: peterlang.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:_spf.google.com ip4:212.18.11.33/27 ip4:167.114.73.155/32 include:mailgun.org ip4:80.82.205.232 ip4:213.164.70.57 include:5381528.spf05.hubspotemail.net ip4:67.228.101.200 include:amazonses.com -all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 9 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

pass

p=reject (_dmarc.peterlang.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:dmarc@peterlang.com;
Found at: _dmarc.peterlang.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:dmarc@peterlang.com	Aggregate report addresses

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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@peterlang.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

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

Signed, DS published at parent

Found

DNSKEY records: Yes (4)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 56802, 16144, 56067, 51951
Signatures valid until: 26 October 2026, 16:29 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
!

Signatures expire in 102h0m0s

DNSKEY signatures expire at 2026-10-26T16:29:12Z (in 102h0m0s). Check that re-signing works.

#21

MX

warn

6 mail servers

Found

Priority	Host	Records	Reverse DNS
0	peterlang-com.mail.protection.outlook.com	A 52.101.185.12 A 52.101.185.14 A 52.101.187.1 A 52.101.185.13 AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:ca09::22	mail-zrap278cu00304.inbound.protection.outlook.com ✓ mail-zr1p278cu00206.inbound.protection.outlook.com ✓ mail-gvap278cu00301.inbound.protection.outlook.com ✓ mail-zrzp278cu00205.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.inbound.protection.outlook.com ✓
1	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.27 AAAA 2404:6800:4000:1027::1b	ncboms-in-f27.1e100.net ✓ ncboms-in-f27.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.26 AAAA 2404:6800:4013:813::1b	lcdels-in-f26.1e100.net ✓ lcdels-in-f27.1e100.net ✓

Checks

✓ 6 MX records #9

Found 6 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.
✓ Redundant MX hosts #12

Found 6 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

#13
✓ 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 18 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
peterlang-com.mail.protection.outlook.com	none	-
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.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