Mail domain report: liferay.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.mlsend.com include:_spf.google.com exists:%{i}._spf.mta.salesforce.com ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 ip4:135.84.79.54 include:amazonses.com ip4:45.33.96.128 ip6:2600:3c02::f03c:91ff:fe14:bdf4 ip4:45.33.98.230 ip4:45.33.101.178 ip4:45.33.101.248 ip4:45.33.118.117 ip4:45.33.97.236 ip4:45.33.11.193 ip4:45.33.103.156 ip4:45.79.196.43 ip4:45.79.252.254 ip4:45.79.222.81 ip4:45.79.214.43 ip4:45.79.20.199 ip4:45.79.202.146 ip4:45.79.252.128 ip4:45.79.216.192 ip4:45.79.142.135 ip4:173.230.133.211 ip4:173.230.142.88 ip4:173.230.129.192 ip4:173.230.130.162 ip4:173.230.131.119 ip4:173.255.192.145 ip4:173.255.204.177 ip4:74.207.228.242 ip4:45.56.74.214 ip4:50.116.20.99 ip4:50.116.24.128 ip4:50.116.47.103 ip4:50.116.33.90 ip4:198.58.122.160 ip4:96.126.114.131 ip4:66.228.62.233 ip4:23.92.29.181 ip4:74.207.233.23 ip4:66.228.58.178 ip4:198.58.109.76 ip4:45.56.126.250 ip4:194.195.213.189 ip4:172.105.149.213 ip4:170.187.206.60 ip4:170.187.206.248 ip4:170.187.206.159 ip4:170.187.141.20 ip4:170.187.141.29 ip4:170.187.141.126 ip4:170.187.159.57 ip4:170.187.149.178 ip4:170.187.205.16 ip4:170.187.144.56 ip4:170.187.157.148 ip4:66.228.60.125 ip4:172.105.151.149 ip4:173.230.132.235 ip4:173.230.130.162 ip6:2600:3c02::f03c:91ff:fe14:bd66 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip4:130.248.172.0/24 ip4:130.248.173.0/24 include:oktamail.liferay.com ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:173.196.61.235 ip4:87.213.68.70/32 ip4:173.196.61.236 -all
DNS lookups: 5 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 5 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.liferay.com)

Found

Record: v=DMARC1; p=quarantine; sp=none; rua=mailto:re+xr4jsquuon2@dmarc.postmarkapp.com,mailto:dmarc@inbound.flowmailer.net; ruf=mailto:dmarc@inbound.flowmailer.net; adkim=r; aspf=r; fo=1;
Found at: _dmarc.liferay.com
External report address: mailto:re+xr4jsquuon2@dmarc.postmarkapp.com (authorized)
External report address: mailto:dmarc@inbound.flowmailer.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
rua	mailto:re+xr4jsquuon2@dmarc.postmarkapp.com,mailto:dmarc@inbound.flowmailer.net	Aggregate report addresses
ruf	mailto:dmarc@inbound.flowmailer.net	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
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 100% of mail #18

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

Aggregate reports are sent to: mailto:re+xr4jsquuon2@dmarc.postmarkapp.com, mailto:dmarc@inbound.flowmailer.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: k1, google, s1, s2

Found

Selectors: k1, google, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: k1, google, s1, s2 #7

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

1024-bit DKIM key

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

warn

Signed, but no DS at parent

Found

DNSKEY records: Yes (2)
DS at parent: No
Algorithms: ECDSAP256SHA256 (13)
Key tags: 2371, 34505
Signatures valid until: 8 December 2026, 11:50 UTC

Checks

!

Signed, but no DS at parent

The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

#8
✓ Signatures valid until 2026-12-08 #21

DNSKEY signatures are valid until 2026-12-08T11:50:11Z.

MX

warn

7 mail servers

Found

Priority	Host	Records	Reverse DNS
10	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 ✓
20	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
20	alt2.aspmx.l.google.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.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.26 AAAA 2404:6800:4013:813::1b	lcdels-in-f26.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 enforce · no TLS-RPT · DANE on 0 of 7 MX hosts

Found

MTA-STS record: v=STSv1; id=175459540041;
Policy URL: https://mta-sts.liferay.com/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com
Max age: 604800 seconds

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 175459540041.
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 168h0m0s.
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
!

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
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