Mail domain report: idp.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf-dc10.sapsf.com include:1860138.spf05.hubspotemail.net include:mktomail.com include:emailsrvr.com include:au._netblocks.mimecast.com include:spf_ip.idp.com include:_spf.general.transactional-mail-a.com include:spf.protection.outlook.com ~all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 8 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

fail

p=none (_dmarc.idp.com)

Found

Record: v=DMARC1; p=none; adkim=r; aspf=r; rua=mailto:dmarc-reports@idp.com; fo=1
Found at: _dmarc.idp.com

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:dmarc-reports@idp.com	Aggregate 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: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc-reports@idp.com
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: k1, selector1, selector2

Found

Selectors: k1, selector1, selector2
_domainkey: NXDOMAIN

Selector	Key	Flags
k1	RSA 1024 bits
selector1	RSA 1024 bits
selector2	RSA 2048 bits

Checks

✓ Keys found: k1, selector1, selector2 #7

DKIM keys found for this domain with selectors: k1, selector1, selector2
!

1024-bit DKIM key

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

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

1 mail server

Found

Priority	Host	Records	Reverse DNS
5	idp-com.mail.protection.outlook.com	A 52.101.137.0 A 52.101.157.80 A 52.101.137.2 A 52.101.124.117 AAAA 2a01:111:f403:cc09:: AAAA 2a01:111:f403:cc09::1 AAAA 2a01:111:f403:cc1a::8 AAAA 2a01:111:f403:cc1f::4	mail-sg2pr03cu00500.inbound.protection.outlook.com ✓ mail-os8pr02cu00100.inbound.protection.outlook.com ✓ no PTR mail-tydpr03cu00105.inbound.protection.outlook.com ✓ mail-sg2pr03cu00500.inbound.protection.outlook.com ✓ no PTR mail-tydpr03cu00100.inbound.protection.outlook.com ✓ mail-os8pr02cu00104.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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (idp-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (idp-com.mail.protection.outlook.com). Ask your hosting provider to set one.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
idp-com.mail.protection.outlook.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

fail

https://idp-email-bimi-logo.s3.ap-southeast-2.amazonaws.com/Logo.svg

Found

Record: v=BIMI1;l=https://idp-email-bimi-logo.s3.ap-southeast-2.amazonaws.com/Logo.svg
Found at: default._bimi.idp.com
Logo: https://idp-email-bimi-logo.s3.ap-southeast-2.amazonaws.com/Logo.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✗

DMARC not strict enough for BIMI

Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.

#39