Skip to content
https://www.mybts.fr

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
17
6 PASS 10 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
DNS Records
1 A records, 307 ms lookup
REVIEW
1 A records, 307 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.125.27.5
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:1600:0:aaaa::80:4
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (307 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 307 ms
A185.125.27.5
AAAA2001:1600:0:aaaa::80:4
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 307 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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

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 185.125.27.5 does not match any cert SAN: h2web389.infomaniak.ch
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 for 2001:1600:0:aaaa::80:4 does not match any cert SAN: h2web389.infomaniak.ch
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.
B
Multi-Resolver DNS Speed
Mean 61ms across 3 resolvers (spread 169ms)
REVIEW
Mean 61ms across 3 resolvers (spread 169ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 12ms
Got: 12ms via 8.8.8.8:53
Info::
Quad9: 171ms
Got: 171ms via 9.9.9.9:53
C
HTTP Probe Timing
Action
Total 1792 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
290 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
145 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
149 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.65 s
Total Time Total request time from DNS lookup through full response.
1.79 s

Connection waterfall

DNS Lookup 290 ms TCP Connect 145 ms TLS Handshake 149 ms Server Processing 1.06 s Content Transfer 146 ms
B
TLS Certificate Expiry & Recommendations
54 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.mybts.fr

https://www.mybts.fr

1714 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.mybts.fr2001714 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (150 ms)
PASS
IPv6 reachable (150 ms)
Info::
IPv6 is configured and reachable at 2001:1600:0:aaaa::80:4
Got: 150 ms connect
IPv6 Ready
AAAA Records 2001:1600:0:aaaa::80:4 Connection Reachable (150 ms)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 887 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 887 B Sitemaps referenced 1 User-agents GPTBot, *, CCBot, DotBot, MegaIndex, Yandex, Google-Extended, PerplexityBot, AhrefsBot, PetalBot, ClaudeBot, Applebot-Extended, MJ12bot, SemrushBot, Baiduspider Blocking No — crawling allowed
User-agent: *
Allow: /wp-admin/admin-ajax.php

# Zones sensibles WordPress
Disallow: /wp-admin/
Disallow: /wp-login.php
Disallow: /xmlrpc.php

# Zones priv�es du site
Disallow: /forum/
Disallow: /commander/

# Param�tres inutiles SEO
Disallow: /*?replytocom
Disallow: /*?s=

# Blocage de l'entra�nement IA

User-agent: GPTBot
Disallow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

# Scrapers SEO et robots peu utiles

User-agent: DotBot
Disallow: /

User-agent: AhrefsBot
Disallow: /

User-agent: MJ12bot
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: MegaIndex
Disallow: /

User-agent: Yandex
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: PetalBot
Disallow: /

# Sitemap
Sitemap: https://www.mybts.fr/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.mybts.fr/
301https://mybts.fr/

Preferred variant: www

HTTP → HTTPS

301http://www.mybts.fr/ → https://www.mybts.fr/

Consistent

A+
Domain Intelligence
mybts.fr — via Infomaniak Network SA, 15 years, 6 months old
PASS
mybts.fr — via Infomaniak Network SA, 15 years, 6 months old
Info::
Domain registered until May 17, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Infomaniak Network SA
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.
Domain expiry

310 days

May 17, 2027

SSL certificate

54 days

Issued by Let's Encrypt

Domain age

15 years, 6 months

Registered March 11, 2011

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:1600:0:aaaa::80:4

Registrar

Infomaniak Network SA

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Infomaniak Network SA
Created March 11, 2011 (15 years, 6 months ago)
Expires May 17, 2027 (10 months)
Last Updated April 19, 2026
Name Servers nsany1.infomaniak.com, nsany2.infomaniak.com
DNSSEC Enabled
Registrant Domain Privacy Trustee SA
Hosting
IP Address 2001:1600:0:aaaa::80:4
Data source: rdap (0.6s)

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