Skip to content
https://intermarche.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 81.255.44.177 does not match any cert SAN: intermarche.eu
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 91.237.184.177: lookup 91.237.184.177: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
150 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

150
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 31 ms lookup
PASS
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 81.255.44.177, 91.237.184.177
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: rick.ns.cloudflare.com, kelly.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 31 ms
Got: 31 ms
A81.255.44.177, 91.237.184.177
AAAA—
CNAME—
NSrick.ns.cloudflare.com, kelly.ns.cloudflare.com
MX
10 mxa-004e2302.gslb.pphosted.com
10 mxb-004e2302.gslb.pphosted.com
TXT
MS=ms15616510
Validity-Domain-Verification=aSdTtaguIn4q7mR3KqhdhT3SKJc=
xEpKsCrpMP99dORSLJYK4w
google-site-verification=nW5PGmemZVX6PnlRVY9tLqMLieHkkq6cd8B98R6Y_OE
SPF v=spf1 a:smtp.mousquetaires.com include:spf.protection.outlook.com include:spf-0...
facebook-domain-verification=k34ehtyb6xu0ih4eapeit0vl1l23md
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbPIly6vAjuZfZFoYL+IXVtBN1GahUPpS...
CAALookup not available with standard resolver
Resolved in 31 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 24ms across 3 resolvers (spread 13ms)
PASS
Mean 24ms across 3 resolvers (spread 13ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Quad9: 25ms
Got: 25ms via 9.9.9.9:53
Info::
Google: 30ms
Got: 30ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 148 ms total
PASS
1 redirect(s), 148 ms total
Info::
Single redirect
Got: https://intermarche.com → https://www.intermarche.com/ (301)
Info::
WWW normalization redirect

https://intermarche.com

75 ms · HTTP/1.0

301

https://www.intermarche.com/

73 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://intermarche.com30175 msHTTP/1.0BigIP
2https://www.intermarche.com/40373 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 2530 URLs
PASS
robots.txt present, sitemap with 2530 URLs
Info::
robots.txt is present
Got: 412 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2530 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 412 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /magasins/*/*/infos-pratiques
Disallow: /accueil/drive-catalogue/*
Disallow: /magasins/*
Disallow: /rechercheproduits/*
Disallow: /?pdvref*
Disallow: /localisation/*
Disallow: *trier*
Disallow: *voir-tout*
Disallow: /catalogues/*
Disallow: /s/*
Disallow: *?itemId=*
Disallow: /recherche/*
Disallow: /api/*
Disallow: /catalog/*
Disallow: /_next/*
Disallow: /src/components/*
Disallow: *..png*
sitemap.xml 200 OK
Type URL Set URLs 2530 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.intermarche.com/
200https://intermarche.com/

HTTP → HTTPS

301http://intermarche.com/ → https://www.intermarche.com/

Consistent

A+
Domain Intelligence
intermarche.com — via Register.com - Network Solutions, LLC, 30 years old, hosted on AS3215 - Orange S.A., FR
PASS
intermarche.com — via Register.com - Network Solutions, LLC, 30 years old, hosted on AS3215 - Orange S.A., FR
Info::
Domain registered until Oct 20, 2026 (4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Register.com - Network Solutions, LLC
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AS3215 - Orange S.A., FR
Got: AS3215
Domain expiry

138 days

October 20, 2026

SSL certificate

150 days

Issued by Sectigo Limited

Domain age

30 years

Registered October 21, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AS3215 - Orange S.A., FR

ASN AS3215

81.255.44.177

Registrar

Register.com - Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Register.com - Network Solutions, LLC
Created October 21, 1996 (30 years ago)
Expires October 20, 2026 (4 months)
Last Updated September 11, 2025
Name Servers kelly.ns.cloudflare.com, rick.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 81.255.44.177
ASN AS3215 (AS3215 - Orange S.A., FR)
Provider AS3215 - Orange S.A., FR
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 111 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
37 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
22 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
111 ms
Total Time Total request time from DNS lookup through full response.
111 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 22 ms TLS Handshake 29 ms Server Processing 23 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback