Mail domain report: artnet.fr

SPF

pass

SPF record published

Found

Record: v=spf1 -all
DNS lookups: 0 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 0 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=reject (_dmarc.artnet.fr)

Found

Record: v=DMARC1; p=reject; aspf=s; adkim=s; rua=mailto:dmarc-reports@artnet.support
Found at: _dmarc.artnet.fr
External report address: mailto:dmarc-reports@artnet.support (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:dmarc-reports@artnet.support	Aggregate report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)

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-reports@artnet.support
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
!

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-reports@artnet.support (needs artnet.fr._report._dmarc.artnet.support). Ask the report provider to publish the record, or check the address.

#29

DKIM

info

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
default	revoked
dkim	revoked
mail	revoked
email	revoked
k1	revoked
selector1	revoked
selector2	revoked
google	revoked
zoho	revoked
mx	revoked
key	revoked
mta	revoked
pm	revoked
dkim-smtp	revoked
s1	revoked
s2	revoked

Checks

✓ Keys found: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7

DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
i

All keys revoked

All found keys are revoked (empty p=): default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2. That is fine if this domain no longer signs mail.

#24

DNSSEC

pass

Signed, DS published at parent

Found

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

DNSKEY signatures are valid until 2026-12-14T01:50:38Z.

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
10	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 ✓
20	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
20	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
20	alt3.aspmx.l.google.com	A 192.179.20.27 AAAA 2404:6800:4000:1027::1a	ncboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
20	alt4.aspmx.l.google.com	A 192.178.158.27 AAAA 2404:6800:4013:813::1a	lcdels-in-f27.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 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 5 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.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

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