bouygues-es.fr

Checked 22 October 2026, 02:01 UTC · via 8.8.8.8
✗Problems found
20 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:concentrateur.bouygues-construction.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.
  • ✓ 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.bouygues-es.fr)

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc_reports@bouygues-construction.com; ruf=mailto:dmarc_reports@bouygues-construction.com; sp=none;
Found at
_dmarc.bouygues-es.fr
External report address
mailto:dmarc_reports@bouygues-construction.com (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
ruamailto:dmarc_reports@bouygues-construction.comAggregate report addresses
rufmailto:dmarc_reports@bouygues-construction.comFailure report addresses

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_reports@bouygues-construction.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_reports@bouygues-construction.com (needs bouygues-es.fr._report._dmarc.bouygues-construction.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (4)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
360, 34750, 26920, 29752
Signatures valid until
22 October 2026, 10:00 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 expire in 8h0m0s
    DNSKEY signatures expire at 2026-10-22T10:00:00Z (in 8h0m0s). Check that re-signing works.
    #21

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10concentrateur.bouygues-construction.comA 68.232.139.177 A 216.71.159.211 A 216.71.159.242 A 68.232.139.101 A 216.71.139.73 A 216.71.136.224 A 216.71.136.210 A 216.71.139.74 A 216.71.139.72 A 216.71.139.133 A 216.71.159.210 A 68.232.139.39 A 216.71.159.214 A 216.71.139.71 A 216.71.159.212 A 216.71.159.213 A 216.71.159.243 A 216.71.139.75 A 216.71.139.66 A 216.71.139.132esa19.hc979-39.c3s2.iphmx.com ✓ esa9.hc979-39.c3s2.iphmx.com ✓ esa13.hc979-39.c3s2.iphmx.com ✓ esa20.hc979-39.c3s2.iphmx.com ✓ esa3.hc979-39.c3s2.iphmx.com ✓ esa16.hc979-39.c3s2.iphmx.com ✓ esa15.hc979-39.c3s2.iphmx.com ✓ esa4.hc979-39.c3s2.iphmx.com ✓ esa2.hc979-39.c3s2.iphmx.com ✓ esa7.hc979-39.c3s2.iphmx.com ✓ esa8.hc979-39.c3s2.iphmx.com ✓ esa18.hc979-39.c3s2.iphmx.com ✓ esa12.hc979-39.c3s2.iphmx.com ✓ esa1.hc979-39.c3s2.iphmx.com ✓ esa10.hc979-39.c3s2.iphmx.com ✓ esa11.hc979-39.c3s2.iphmx.com ✓ esa14.hc979-39.c3s2.iphmx.com ✓ esa5.hc979-39.c3s2.iphmx.com ✓ esa17.hc979-39.c3s2.iphmx.com ✓ esa6.hc979-39.c3s2.iphmx.com ✓
20secours.bouygues-construction.comA 216.71.139.75 A 68.232.139.101 A 216.71.159.214 A 216.71.159.212 A 68.232.139.39 A 216.71.139.66 A 216.71.159.243 A 216.71.136.224 A 216.71.139.133 A 216.71.159.213 A 216.71.139.72 A 216.71.159.211 A 216.71.136.210 A 216.71.139.74 A 68.232.139.177 A 216.71.159.242 A 216.71.139.132 A 216.71.139.71 A 216.71.139.73 A 216.71.159.210esa5.hc979-39.c3s2.iphmx.com ✓ esa20.hc979-39.c3s2.iphmx.com ✓ esa12.hc979-39.c3s2.iphmx.com ✓ esa10.hc979-39.c3s2.iphmx.com ✓ esa18.hc979-39.c3s2.iphmx.com ✓ esa17.hc979-39.c3s2.iphmx.com ✓ esa14.hc979-39.c3s2.iphmx.com ✓ esa16.hc979-39.c3s2.iphmx.com ✓ esa7.hc979-39.c3s2.iphmx.com ✓ esa11.hc979-39.c3s2.iphmx.com ✓ esa2.hc979-39.c3s2.iphmx.com ✓ esa9.hc979-39.c3s2.iphmx.com ✓ esa15.hc979-39.c3s2.iphmx.com ✓ esa4.hc979-39.c3s2.iphmx.com ✓ esa19.hc979-39.c3s2.iphmx.com ✓ esa13.hc979-39.c3s2.iphmx.com ✓ esa6.hc979-39.c3s2.iphmx.com ✓ esa1.hc979-39.c3s2.iphmx.com ✓ esa3.hc979-39.c3s2.iphmx.com ✓ esa8.hc979-39.c3s2.iphmx.com ✓

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: concentrateur.bouygues-construction.com, secours.bouygues-construction.com
    #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 40 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
concentrateur.bouygues-construction.comnone-
secours.bouygues-construction.comnone-

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