iedom.fr

Checked 22 October 2026, 03:25 UTC · via 8.8.8.8
!Passed with warnings
23 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:176.149.163.103 ip4:176.149.163.104 ip4:195.60.188.95 ip4:158.255.65.100 ip4:149.72.161.246 ip4:149.72.190.43 ip4:149.72.227.21 ip4:167.89.111.77 ip4:168.245.22.106 ip4:168.245.23.37 ip4:168.245.61.128 ip4:168.245.125.167 ip4:69.169.229.106 ip4:69.169.229.107 ip4:69.169.229.110 ip4:69.169.229.111 ip4:69.169.229.112 ip4:69.169.229.113 ip4:69.169.229.114 ip4:69.169.229.115 ip4:202.171.64.23 ip4:202.171.64.46 ip4:202.3.239.161 ip4:202.171.64.23 ip4:202.171.64.46 mx a -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 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=quarantine (_dmarc.iedom.fr)

Found

Record
v=DMARC1; p=quarantine; pct=100; adkim=s; aspf=s
Found at
_dmarc.iedom.fr
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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.
  • !
    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
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.

DKIM

pass

Selectors: default

Found

Selectors
default
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 2048 bits

Checks

  • ✓ Keys found: default #7
    DKIM keys found for this domain with selectors: default
  • ✓ Strong keys #23
    DKIM keys are strong enough: default: RSA 2048 bits.
  • ✓ 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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10smtp.iedom-ieom.frA 176.149.163.104smtp.iedom-ieom.fr ✓
10smtp1.iedom-ieom.frA 176.149.163.103smtp1.iedom-ieom.fr ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: smtp.iedom-ieom.fr, smtp1.iedom-ieom.fr
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
smtp.iedom-ieom.frnone-
smtp1.iedom-ieom.frnone-

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