Mail domain report: udemy.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:mktomail.com include:spf.mtasv.net include:mail.zendesk.com include:_spf.salesforce.com -all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 6 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.udemy.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:dmarc-udemy@udemy.com; ruf=mailto:dmarc-udemy@udemy.com; rf=afrf; fo=1; pct=100
Found at: _dmarc.udemy.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-udemy@udemy.com	Aggregate report addresses
ruf	mailto:dmarc-udemy@udemy.com	Failure report addresses
fo	1	Failure reporting options
rf	afrf	Failure report format

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:dmarc-udemy@udemy.com
✓ Subdomain policy: reject #20

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

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, google, s1, s2

Found

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

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

Checks

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

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

1024-bit DKIM key

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 2371, 34505
Signatures valid until: 11 December 2026, 12:34 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-12-11 #21

DNSKEY signatures are valid until 2026-12-11T12:34:02Z.

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
1	smtp.google.com	A 142.251.127.27 A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
smtp.google.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

pass

https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.svg

Found

Record: v=BIMI1;l=https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.svg; a=https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.pem
Found at: default._bimi.udemy.com
Logo: https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.svg
Certificate: https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.svg; certificate: https://vmc.digicert.com/32fdffab-58c5-4758-9538-013348374892.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.