Skip to content
https://vie-publique.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
4 PASS 4 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.

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.vie-publique.fr/
200https://vie-publique.fr/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://vie-publique.fr/ → https://vie-publique.fr/

Consistent

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

Connection waterfall

DNS Lookup 340 ms TCP Connect 167 ms TLS Handshake 173 ms Server Processing 170 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
309 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

309
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
A
DNS Records
1 A records, 339 ms lookup
PASS
1 A records, 339 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 87.98.187.73
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns2.dila.fr, ns4.dila.fr, ns1.dila.fr, ns3.dila.fr
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (339 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 339 ms
A87.98.187.73
AAAA—
CNAME—
NSns2.dila.fr, ns4.dila.fr, ns1.dila.fr, ns3.dila.fr
MX
10 relay1-c.dila.fr
20 relay2-c.dila.fr
TXT
SPF v=spf1 a mx ip4:160.92.31.25 ip4:160.92.25.181 ip4:160.92.64.52 ip4:162.19.70.41...
CAALookup not available with standard resolver
Resolved in 339 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://vie-publique.fr

https://vie-publique.fr

871 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vie-publique.fr200871 msHTTP/1.1
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 232 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 232 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<html lang="en"><head></head><body><script>window.location.href='/redirect_6TUKNLFGBVS3PKQBCBYY4P2H4DHANX2TJQ6VWY3JBTK4SEP6SRTQ====/robots.txt';</script><noscript>This website requires JS enabled and cookies</noscript></body></html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A
Domain Intelligence
vie-publique.fr — via NAMESHIELD, 24 years, 10 months old, hosted on OVH
PASS
vie-publique.fr — via NAMESHIELD, 24 years, 10 months old, hosted on OVH
Warning::
Domain expires in 67 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 29, 2026
Info::
Registrar: NAMESHIELD
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: OVH
Got: AS16276
Domain expiry

16 days

June 29, 2026

SSL certificate

309 days

Issued by Sectigo Limited

Domain age

24 years, 10 months

Registered October 30, 2001

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

87.98.187.73

Registrar

NAMESHIELD

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NAMESHIELD
Created October 30, 2001 (24 years, 10 months ago)
Expires June 29, 2026 (2 months)
Last Updated July 2, 2025
Name Servers ns1.dila.fr, ns2.dila.fr, ns3.dila.fr, ns4.dila.fr
Registrant Etat francais represente par la Direction de l information legale et administrative DILA
Hosting
IP Address 87.98.187.73
ASN AS16276 (OVH, FR)
Provider OVH
Data source: rdap (1.5s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback