Mail domain report: lawinsider.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:servers.mcsv.net ~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=quarantine (_dmarc.lawinsider.com)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@lawinsider.com
Found at: _dmarc.lawinsider.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:dmarc-reports@lawinsider.com	Aggregate report addresses

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 100% of mail #18

DMARC policy applies to all failing mail.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc-reports@lawinsider.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (3)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 15415, 13434, 10442
Signatures valid until: 10 November 2026, 08:13 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-11-10 #21

DNSKEY signatures are valid until 2026-11-10T08:13:33Z.

MX

warn

7 mail servers

Found

Priority	Host	Records	Reverse DNS
10	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 ✓
20	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1a	rd-in-f27.1e100.net ✓ rd-in-f26.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.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
30	aspmx3.googlemail.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.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::1b	lcdels-in-f27.1e100.net ✓ lcdels-in-f27.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

warn

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

Found

MTA-STS record: v=STSv1;id=1755304803198;
Policy URL: https://mta-sts.lawinsider.com/.well-known/mta-sts.txt
Mode: testing
Allowed MX: aspmx4.googlemail.com, aspmx3.googlemail.com, aspmx2.googlemail.com, alt1.aspmx.l.google.com, aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx5.googlemail.com
Max age: 604800 seconds
TLS-RPT record: v=TLSRPTv1;rua=mailto:smtp-tls-reports@lawinsider.com;

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 1755304803198.
!

Policy in testing mode

With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

#33
✓ 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:smtp-tls-reports@lawinsider.com
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