melty.fr

Checked 22 October 2026, 04:18 UTC · via 8.8.8.8
✗Problems found
17 passed 3 warnings 2 failed 5 info

SPF

fail

SPF record published

Found

Record
v=spf1 78.109.95.0/25 91.220.85.0/24 include:_spf.google.com ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 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.
  • ✗
    Syntax errors
    Receivers reject the whole SPF record (permerror) because of: unknown mechanism "78.109.95.0/25"; unknown mechanism "91.220.85.0/24".
    #25
  • ✓ 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.melty.fr)

Found

Record
v=DMARC1; p=none
Found at
_dmarc.melty.fr
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

info

DNS query for _domainkey.melty.fr failed: read udp 46.225.38.91:51749->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The DKIM lookup failed, so this could not be checked: DNS query for _domainkey.melty.fr failed: read udp 46.225.38.91:51749->8.8.8.8:53: i/o timeout
    #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

PriorityHostRecordsReverse DNS
10aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
20alt1.aspmx.l.google.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1ard-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
20alt2.aspmx.l.google.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1byulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
30aspmx2.googlemail.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1ard-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
30aspmx3.googlemail.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
30aspmx4.googlemail.comA 192.179.20.27 AAAA 2404:6800:4000:1027::1ancboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
30aspmx5.googlemail.comA 192.178.158.26 AAAA 2404:6800:4013:813::1blcdels-in-f26.1e100.net ✓ lcdels-in-f27.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.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ 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 14 MX addresss have a PTR record that resolves back to them.

TLS

info

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
aspmx2.googlemail.comnone-
aspmx3.googlemail.comnone-
aspmx4.googlemail.comnone-
aspmx5.googlemail.comnone-
Lookup error: DNS query for _mta-sts.melty.fr failed: read udp 46.225.38.91:54505->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The MTA-STS lookup failed, so this could not be checked: DNS query for _mta-sts.melty.fr failed: read udp 46.225.38.91:54505->8.8.8.8:53: i/o timeout
    #32
  • i
    Could not be checked
    The TLS-RPT lookup failed, so this could not be checked: DNS query for _smtp._tls.melty.fr failed: read udp 46.225.38.91:55478->8.8.8.8:53: i/o timeout
    #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

DNS query for default._bimi.melty.fr failed: read udp 46.225.38.91:49258->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The BIMI lookup failed, so this could not be checked: DNS query for default._bimi.melty.fr failed: read udp 46.225.38.91:49258->8.8.8.8:53: i/o timeout
    #38