Mail domain report: lottiefiles.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com include:47508472.spf08.hubspotemail.net ip4:168.235.224.0/20 ip4:162.247.112.0/21 ip4:209.133.224.0/19 ~all
DNS lookups: 4 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 4 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.lottiefiles.com)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:60706cd31c0b4210853d27cbbbae582f@dmarc-reports.cloudflare.net; ruf=mailto:dmarc+forensic@lottiefiles.com; fo=1; sp=none; pct=50
Found at: _dmarc.lottiefiles.com
External report address: mailto:60706cd31c0b4210853d27cbbbae582f@dmarc-reports.cloudflare.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
pct	50	Percentage of mail the policy applies to
rua	mailto:60706cd31c0b4210853d27cbbbae582f@dmarc-reports.cloudflare.net	Aggregate report addresses
ruf	mailto:dmarc+forensic@lottiefiles.com	Failure report addresses
fo	1	Failure reporting options

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

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

#18
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:60706cd31c0b4210853d27cbbbae582f@dmarc-reports.cloudflare.net
!

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: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: google, s1, s2 #7

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

1024-bit DKIM key

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 2371, 34505
Signatures valid until: 12 December 2026, 15:44 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 valid until 2026-12-12 #21

DNSKEY signatures are valid until 2026-12-12T15:44:18Z.

MX

warn

8 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5	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 ✓
5	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.26 AAAA 2404:6800:4000:1027::1b	ncboms-in-f26.1e100.net ✓ ncboms-in-f27.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.27 AAAA 2404:6800:4013:813::1b	lcdels-in-f27.1e100.net ✓ lcdels-in-f27.1e100.net ✓
10	mxa.mailgun.org	A 34.36.182.139	139.182.36.34.bc.googleusercontent.com ✓
10	mxb.mailgun.org	A 34.149.254.5	5.254.149.34.bc.googleusercontent.com ✓
15	u6h37u4granhtgexnbplg6yiiujlpzavf2nkih6nfqwsxe7z6jbq.mx-verification.google.com	(does not resolve)

Checks

✓ 8 MX records #9

Found 8 MX records for this domain.
!

Hosts without IP addresses

The following MX hosts could not be resolved to IP addresses: u6h37u4granhtgexnbplg6yiiujlpzavf2nkih6nfqwsxe7z6jbq.mx-verification.google.com

#10
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mxa.mailgun.org, mxb.mailgun.org, u6h37u4granhtgexnbplg6yiiujlpzavf2nkih6nfqwsxe7z6jbq.mx-verification.google.com

#11
✓ Redundant MX hosts #12

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

More than 5 MX records

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
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	-
mxa.mailgun.org	none	-
mxb.mailgun.org	none	-
u6h37u4granhtgexnbplg6yiiujlpzavf2nkih6nfqwsxe7z6jbq.mx-verification.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