Mail domain report: prometric.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:208.76.122.9 ip4:208.76.123.9 ip4:104.130.47.71 ip4:149.72.131.17 ip4:149.72.155.253 include:spf1.prometric.com include:spf.protection.outlook.com include:_spf.salesforce.com include:spf.mailjet.com include:_spf.advansys.com -all
DNS lookups: 10 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 10 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.prometric.com)

Found

Record: v=DMARC1;p=quarantine;sp=quarantine;pct=100;rua=mailto:dmarc-reports@prometric.com;ruf=mailto:dmarc-reports@prometric.com;aspf=r;adkim=r
Found at: _dmarc.prometric.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-reports@prometric.com	Aggregate report addresses
ruf	mailto:dmarc-reports@prometric.com	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

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@prometric.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: selector1, s1, s2

Found

Selectors: selector1, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: selector1, s1, s2 #7

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

1024-bit DKIM key

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

warn

Signed, DS published at parent

Found

DNSKEY records: Yes (3)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 32991, 14439, 10430
Signatures valid until: 24 October 2026, 18:02 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 expire in 56h0m0s

DNSKEY signatures expire at 2026-10-24T18:02:21Z (in 56h0m0s). Check that re-signing works.

#21

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	prometric-com.mail.protection.outlook.com	A 52.101.41.24 A 52.101.40.5 A 52.101.60.2 A 52.101.42.81 AAAA 2a01:111:f403:c927::1 AAAA 2a01:111:f403:f805::4 AAAA 2a01:111:f403:f904::d AAAA 2a01:111:f403:c946::10	mail-sj0pr03cu01600.inbound.protection.outlook.com ✓ mail-cy4pr03cu00105.inbound.protection.outlook.com ✓ mail-bnypr05cu00102.inbound.protection.outlook.com ✓ mail-ea2pr04cu00101.inbound.protection.outlook.com ✓ mail-bn8pr05cu00301.inbound.protection.outlook.com ✓ mail-mw2pr05cu00104.inbound.protection.outlook.com ✓ mail-dm2pr03cu00105.inbound.protection.outlook.com ✓ mail-ch4pr04cu00300.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 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.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

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

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=20211201000000Z
Policy URL: https://mta-sts.prometric.com/.well-known/mta-sts.txt
Policy error: Get "https://mta-sts.prometric.com/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.prometric.com on 127.0.0.53:53: no such host

DANE (TLSA records)

MX host	TLSA	DNSSEC
prometric-com.mail.protection.outlook.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 20211201000000Z.
✗

Policy not reachable

The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.prometric.com/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.prometric.com on 127.0.0.53:53: no such host.

#33
!

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