lw.com

Checked 22 October 2026, 09:41 UTC · via 8.8.8.8
!Passed with warnings
23 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a ip4:136.179.7.175 ip4:136.179.7.176 ip4:136.179.7.177 ip4:136.179.7.178 -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

pass

p=reject (_dmarc.lw.com)

Found

Record
v=DMARC1; p=reject; fo=0; ri=3600; rua=mailto:latham-and-watkins-llp@rua.agari.com; ruf=mailto:latham-and-watkins-llp@ruf.agari.com
Found at
_dmarc.lw.com
External report address
mailto:latham-and-watkins-llp@rua.agari.com (authorized)
External report address
mailto:latham-and-watkins-llp@ruf.agari.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:latham-and-watkins-llp@rua.agari.comAggregate report addresses
rufmailto:latham-and-watkins-llp@ruf.agari.comFailure report addresses
fo0Failure reporting options
ri3600Report 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:latham-and-watkins-llp@rua.agari.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #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

4 mail servers

Found

PriorityHostRecordsReverse DNS
5mx1.lw.comA 66.116.117.70 A 66.116.117.68mx1.lw.com ✓ mx1.lw.com ✓
5mx2.lw.comA 66.116.117.69 A 66.116.117.71mx2.lw.com ✓ mx2.lw.com ✓
5mx3.lw.comA 142.215.42.110 A 142.215.42.111mx3.lw.com ✓ mx3.lw.com ✓
5mx4.lw.comA 142.215.42.109mx4.lw.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx1.lw.com, mx2.lw.com, mx3.lw.com, mx4.lw.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 7 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.lw.comnone-
mx2.lw.comnone-
mx3.lw.comnone-
mx4.lw.comnone-

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