Mail domain report: htcdev.com

SPF

fail

SPF record published

Found

Record: v=spf1 ip4:54.205.153.234 ip4: 54.87.141.62 include:amazonses.com include:_spf.google.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.
✗

Syntax errors

Receivers reject the whole SPF record (permerror) because of: "ip4:": ip4 needs a value; unknown mechanism "54.87.141.62".

#25
✓ 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.htcdev.com)

Found

Record: v=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:no-reply@htcdev.com;ruf=mailto:no-reply@htcdev.com;ri=86400
Found at: _dmarc.htcdev.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:no-reply@htcdev.com	Aggregate report addresses
ruf	mailto:no-reply@htcdev.com	Failure report addresses
ri	86400	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:no-reply@htcdev.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

fail

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NXDOMAIN

Checks

✗

No DKIM keys published

_domainkey.htcdev.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#7

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

6 mail servers

Found

Priority	Host	Records	Reverse DNS
10	inbound-smtp.us-east-1.amazonaws.com	A 44.210.166.32 A 54.197.5.236 A 3.211.210.226 A 54.164.173.191 A 44.206.9.87	ec2-44-210-166-32.compute-1.amazonaws.com ✓ ec2-54-197-5-236.compute-1.amazonaws.com ✓ ec2-3-211-210-226.compute-1.amazonaws.com ✓ ec2-54-164-173-191.compute-1.amazonaws.com ✓ ec2-44-206-9-87.compute-1.amazonaws.com ✓
15	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	aspmx3.googlemail.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
25	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	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
40	aspmx2.googlemail.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.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.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: inbound-smtp.us-east-1.amazonaws.com

#11
✓ 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 15 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
inbound-smtp.us-east-1.amazonaws.com	none	-
alt1.aspmx.l.google.com	none	-
aspmx3.googlemail.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx.l.google.com	none	-
aspmx2.googlemail.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