Mail domain report: stgermain.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com include:amazonses.com include:servers.mcsv.net ~all
DNS lookups: 4 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 4 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.stgermain.fr)

Found

Record: v=DMARC1; p=none; rua=mailto:dmarc-report@bacardi.com; ruf=mailto:dmarc-report@bacardi.com; fo=1; pct=100; ri=3600
Found at: _dmarc.stgermain.fr
External report address: mailto:dmarc-report@bacardi.com (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-report@bacardi.com	Aggregate report addresses
ruf	mailto:dmarc-report@bacardi.com	Failure report addresses
fo	1	Failure reporting options
ri	3600	Report interval (seconds)

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-report@bacardi.com
!

Report address not authorized

These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-report@bacardi.com (needs stgermain.fr._report._dmarc.bacardi.com). Ask the report provider to publish the record, or check the address.

#29

DKIM

fail

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NXDOMAIN

Checks

✗

No DKIM keys published

_domainkey.stgermain.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#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

7 mail servers

Found

Priority	Host	Records	Reverse DNS
0	inbound-smtp.us-east-1.amazonaws.com	A 54.164.173.191 A 44.210.166.32 A 44.206.9.87 A 54.197.5.236 A 3.211.210.226	ec2-54-164-173-191.compute-1.amazonaws.com ✓ ec2-44-210-166-32.compute-1.amazonaws.com ✓ ec2-44-206-9-87.compute-1.amazonaws.com ✓ ec2-54-197-5-236.compute-1.amazonaws.com ✓ ec2-3-211-210-226.compute-1.amazonaws.com ✓
1	stgermain-fr.mail.protection.outlook.com	A 52.101.50.13 A 52.101.8.38 A 52.101.60.71 A 52.101.41.54 AAAA 2a01:111:f403:c922::4 AAAA 2a01:111:f403:c802::2 AAAA 2a01:111:f403:c902::7 AAAA 2a01:111:f403:f905::4	mail-mw2pr02cu00605.inbound.protection.outlook.com ✓ mail-dm3pr04cu00106.inbound.protection.outlook.com ✓ mail-bn0pr02cu00307.inbound.protection.outlook.com ✓ mail-sj2pr05cu00506.inbound.protection.outlook.com ✓ mail-bl1pr02cu00104.inbound.protection.outlook.com ✓ mail-cy3pr05cu00202.inbound.protection.outlook.com ✓ mail-sj0pr02cu00107.inbound.protection.outlook.com ✓ mail-dm2pr04cu00404.inbound.protection.outlook.com ✓
2	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	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 ✓
5	alt2.aspmx.l.google.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10	aspmx2.googlemail.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
10	aspmx3.googlemail.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.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.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: inbound-smtp.us-east-1.amazonaws.com

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
inbound-smtp.us-east-1.amazonaws.com	none	-
stgermain-fr.mail.protection.outlook.com	none	-
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	-

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