Mail domain report: levelblue.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf-core.levelblue.com include:_spf-att.levelblue.com include:_spf-b.levelblue.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

warn

p=quarantine (_dmarc.levelblue.com)

Found

Record: v=DMARC1; p=quarantine; pct=10; sp=none; rua=mailto:re+wrfo0lqzppd@dmarc.postmarkapp.com, mailto:dmarcrua@levelblue.com; ruf=mailto:dmarc_fr@dmarc.everest.email; fo=1; adkim=r; aspf=r; rf=afrf
Found at: _dmarc.levelblue.com
External report address: mailto:re+wrfo0lqzppd@dmarc.postmarkapp.com (authorized)
External report address: mailto:dmarc_fr@dmarc.everest.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
pct	10	Percentage of mail the policy applies to
rua	mailto:re+wrfo0lqzppd@dmarc.postmarkapp.com, mailto:dmarcrua@levelblue.com	Aggregate report addresses
ruf	mailto:dmarc_fr@dmarc.everest.email	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

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 10% of mail

DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.

#18
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:re+wrfo0lqzppd@dmarc.postmarkapp.com, mailto:dmarcrua@levelblue.com
!

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

pass

Selectors: selector1

Found

Selectors: selector1
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits

Checks

✓ Keys found: selector1 #7

DKIM keys found for this domain with selectors: selector1
✓ Strong keys #23

DKIM keys are strong enough: selector1: RSA 2048 bits.
✓ 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	mx.us.mailmarshal.cloud	A 20.81.234.0 A 52.165.80.64 AAAA 2602:f8d5:a1:8001:: AAAA 2602:f8d5:a1:1::	mx.us.mailmarshal.cloud ✓ mx.us.mailmarshal.cloud ✓ mx.us.mailmarshal.cloud ✓ mx.us.mailmarshal.cloud ✓

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx.us.mailmarshal.cloud	3 1 1 06e7ab1436ce4270…	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 1 MX host 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