Skip to content
https://strictmx.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
17
11 PASS 5 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
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 15.235.80.115 does not match any cert SAN: mail.cyborg.ovh
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.
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
89 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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.
A+
DNS Records
1 A records, 31 ms lookup
PASS
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 15.235.80.115
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns109.ovh.net, dns109.ovh.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 31 ms
Got: 31 ms
A15.235.80.115
AAAA—
CNAME—
NSns109.ovh.net, dns109.ovh.net
MX
10 mail.cyborg.ovh
TXT
SPF v=spf1 mx -all
google-site-verification=XnfXKJGe7_KAGVfLvHrR_uwehUqda4WrxD0oxaTciY0
CAALookup not available with standard resolver
Resolved in 31 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA256)
A+
CAA Records
issue: letsencrypt.org | iodef configured
PASS
issue: letsencrypt.org | iodef configured
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org
Info::
CAA iodef tag present (failed-issuance notifications enabled)
A+
Multi-Resolver DNS Speed
Mean 31ms across 3 resolvers (spread 34ms)
PASS
Mean 31ms across 3 resolvers (spread 34ms)
Info::
Quad9: 15ms
Got: 15ms via 9.9.9.9:53
Info::
Cloudflare: 31ms
Got: 31ms via 1.1.1.1:53
Info::
Google: 49ms
Got: 49ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://strictmx.com

https://strictmx.com

300 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://strictmx.com200300 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 979 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 979 B Sitemaps referenced 1 User-agents Applebot-Extended, CCBot, *, GPTBot, OAI-SearchBot, Claude-SearchBot, Perplexity-User, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended Blocking No — crawling allowed
User-agent: *
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: GPTBot
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: OAI-SearchBot
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: ChatGPT-User
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: ClaudeBot
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: Claude-User
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: Claude-SearchBot
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: PerplexityBot
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: Perplexity-User
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: Google-Extended
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: Applebot-Extended
Disallow: /admin
Disallow: /intake
Disallow: /check/

User-agent: CCBot
Disallow: /admin
Disallow: /intake
Disallow: /check/

Sitemap: https://strictmx.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 10 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::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.strictmx.com/
200https://strictmx.com/

Preferred variant: non-www

HTTP → HTTPS

308http://strictmx.com/ → https://strictmx.com/

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
strictmx.com — via OVH sas, 2 months old, hosted on OVH
PASS
strictmx.com — via OVH sas, 2 months old, hosted on OVH
Info::
Domain registered until May 22, 2027 (9 months remaining)
Info::
Domain is only 2 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered May 22, 2026
Info::
DNSSEC is enabled
Info::
Registrar: OVH sas
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

269 days

May 22, 2027

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

2 months

Registered May 22, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

15.235.80.115

Registrar

OVH sas

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar OVH sas
Created May 22, 2026 (2 months ago)
Expires May 22, 2027 (9 months)
Last Updated May 22, 2026
Name Servers dns109.ovh.net, ns109.ovh.net
DNSSEC Enabled
Hosting
IP Address 15.235.80.115
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: rdap (0.8s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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 545 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
24 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
160 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
183 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
545 ms
Total Time Total request time from DNS lookup through full response.
545 ms

Connection waterfall

DNS Lookup 24 ms TCP Connect 160 ms TLS Handshake 183 ms Server Processing 177 ms Content Transfer 1 ms
A+
Health Check Endpoint
Health endpoint at https://strictmx.com/healthz (HTTP 200)
PASS
Health endpoint at https://strictmx.com/healthz (HTTP 200)
Info::
Public health endpoint at https://strictmx.com/healthz
Got: https://strictmx.com/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback