Mail domain report: wral.com

SPF

warn

SPF record published

Found

Record: v=spf1 ip4:64.128.222.0/24 include:spf.protection.outlook.com include:spf-0068f902.pphosted.com include:secondstreetmail.com include:amazonses.com include:aspmx.sailthru.com a mx ~all
DNS lookups: 7 of 10
Void lookups: 1 of 2
Problem: include:spf-0068f902.pphosted.com does not exist or has no records

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
!

7 of 10 DNS lookups, with problems

SPF record needs 7 DNS lookups (limit is 10). Problems found: include:spf-0068f902.pphosted.com does not exist or has no records.

#2
✓ 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.
!

1 void lookup

1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

#26
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.wral.com)

Found

Record: v=DMARC1;p=none;
Found at: _dmarc.wral.com

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19

DKIM

warn

Selectors: selector1

Found

Selectors: selector1
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 1024 bits

Checks

✓ Keys found: selector1 #7

DKIM keys found for this domain with selectors: selector1
!

1024-bit DKIM key

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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mxa.global.inbound.cf-emailsecurity.net	A 141.101.90.40	no PTR
10	mxb.global.inbound.cf-emailsecurity.net	A 141.101.90.40	no PTR

Checks

✓ 2 MX records #9

Found 2 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: mxa.global.inbound.cf-emailsecurity.net, mxb.global.inbound.cf-emailsecurity.net

#11
✓ Redundant MX hosts #12

Found 2 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 2 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: 141.101.90.40 (mxa.global.inbound.cf-emailsecurity.net), 141.101.90.40 (mxb.global.inbound.cf-emailsecurity.net). Ask your hosting provider to set one.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mxa.global.inbound.cf-emailsecurity.net	3 1 1 7fed38b4b0b86d8a… 3 1 1 64f37496c62dd535… 3 1 1 66928f8426b14ef2… 3 1 1 96c2b0229b798135… 3 1 1 8e4d63a1e1f68c76… 3 1 1 8dcca72bfe3c99e7… 3 1 1 e8a50fb03ed780a4… 3 1 1 ea0594ba88c82c58… 3 1 1 9122be3be7bcc604… 3 1 1 e2e4ff54d68bc2aa… 3 1 1 a07b590f83a529f9… 3 1 1 10ba5e544c24746e…	Yes
mxb.global.inbound.cf-emailsecurity.net	3 1 1 7fed38b4b0b86d8a… 3 1 1 64f37496c62dd535… 3 1 1 ea0594ba88c82c58… 3 1 1 9122be3be7bcc604… 3 1 1 96c2b0229b798135… 3 1 1 8dcca72bfe3c99e7… 3 1 1 10ba5e544c24746e… 3 1 1 e8a50fb03ed780a4… 3 1 1 8e4d63a1e1f68c76… 3 1 1 e2e4ff54d68bc2aa… 3 1 1 a07b590f83a529f9… 3 1 1 66928f8426b14ef2…	Yes

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ DANE on all MX hosts #36

All 2 MX hosts publish DNSSEC-validated TLSA records.

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