Mail domain report: worldpoliticsreview.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_u.worldpoliticsreview.com._spf.smart.ondmarc.com ~all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 2 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=reject (_dmarc.worldpoliticsreview.com)

Found

Record: v=DMARC1; p=reject; pct=100; sp=none; rua=mailto:96aaa042@inbox.us.redsift.cloud; ruf=mailto:96aaa042@inbox.us.redsift.cloud; adkim=r; aspf=r; fo=1; rf=afrf; ri=3600
Found at: _dmarc.worldpoliticsreview.com
External report address: mailto:96aaa042@inbox.us.redsift.cloud (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:96aaa042@inbox.us.redsift.cloud	Aggregate report addresses
ruf	mailto:96aaa042@inbox.us.redsift.cloud	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	1	Failure reporting options
rf	afrf	Failure report format
ri	3600	Report interval (seconds)

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:96aaa042@inbox.us.redsift.cloud
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, google

Found

Selectors: k1, google
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits
google	RSA 1024 bits

Checks

✓ Keys found: k1, google #7

DKIM keys found for this domain with selectors: k1, google
!

1024-bit DKIM key

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

7 mail servers

Found

Priority	Host	Records	Reverse DNS
10	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 ✓
20	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
20	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
30	aspmx2.googlemail.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
30	aspmx3.googlemail.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
30	aspmx4.googlemail.com	A 192.179.20.26 AAAA 2404:6800:4000:1027::1a	ncboms-in-f26.1e100.net ✓ ncboms-in-f26.1e100.net ✓
30	aspmx5.googlemail.com	A 192.178.158.27 AAAA 2404:6800:4013:813::1a	lcdels-in-f27.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 7 MX records #9

Found 7 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 7 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 7 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 14 MX addresss have a PTR record that resolves back to them.

TLS

info

MTA-STS enforce · TLS-RPT · DANE on 0 of 7 MX hosts

Found

MTA-STS record: v=STSv1; id=1756456362080
Policy URL: https://mta-sts.worldpoliticsreview.com/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com
Max age: 1209600 seconds
TLS-RPT record: v=TLSRPTv1; rua=mailto:96aaa042@inbox.us.redsift.cloud;

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx2.googlemail.com	none	-
aspmx3.googlemail.com	none	-
aspmx4.googlemail.com	none	-
aspmx5.googlemail.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 1756456362080.
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 336h0m0s.
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
✓ Reports enabled #35

TLS reports are sent to: mailto:96aaa042@inbox.us.redsift.cloud
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