Skip to content
https://mcpl.ai

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
17
6 PASS 10 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a02:4780:84:306b:ccb:d06b:cc72:cfaa, 2a02:4780:84:be4f:752a:2196:3e59:e9ff
Info::
IPv6 connection error
Got: dial tcp6 [2a02:4780:84:306b:ccb:d06b:cc72:cfaa]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a02:4780:84:306b:ccb:d06b:cc72:cfaa, 2a02:4780:84:be4f:752a:2196:3e59:e9ff Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 88.222.222.117 does not match any cert SAN: 88-222-222-117.init.lt
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 2.57.91.114: lookup 2.57.91.114: 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.
Info::
PTR lookup failed for 2a02:4780:84:306b:ccb:d06b:cc72:cfaa: lookup 2a02:4780:84:306b:ccb:d06b:cc72:cfaa: 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.
Info::
PTR lookup failed for 2a02:4780:84:be4f:752a:2196:3e59:e9ff: lookup 2a02:4780:84:be4f:752a:2196:3e59:e9ff: 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.
B
Redirect Chain
1 redirect(s), 1058 ms total
REVIEW
1 redirect(s), 1058 ms total
Info::
Single redirect
Got: https://mcpl.ai → https://www.mcpl.ai/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1058 ms total
Got: 1058 ms

https://mcpl.ai

136 ms · HTTP/1.1

301

https://www.mcpl.ai/

921 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mcpl.ai301136 msHTTP/1.1hcdn
2https://www.mcpl.ai/200921 msHTTP/1.1hcdn

See the visual redirect chain in the HTTP Probe tab →

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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.mcpl.ai/
200https://mcpl.ai/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://mcpl.ai/ → https://www.mcpl.ai/

Consistent

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

Certificate validity

62
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
C
CDN & Delivery
Action
Assets on Cloudflare (host assets.zyrosite.com, 26 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host assets.zyrosite.com, 26 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (assets.zyrosite.com, 26 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a3e08a009dc946f8-SJC
Info::
Assets on Cloudflare: assets.zyrosite.com (assets: 26), cache HIT
Got: cf-ray: a3e08a009dc946f8-SJC
Info::
Assets on Fastly: images.unsplash.com (assets: 5), cache MISS, MISS
Got: delegation dualstack.com.imgix.map.fastly.net
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • assets.zyrosite.com — Cloudflare · assets: 26 · Cache Status: HIT
  • images.unsplash.com — Fastly · assets: 5 · Cache Status: MISS, MISS

Other asset hosts

  • cdn.zyrosite.com — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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, 348 ms lookup
PASS
2 A records, 348 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 88.222.222.117, 2.57.91.114
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:4780:84:306b:ccb:d06b:cc72:cfaa, 2a02:4780:84:be4f:752a:2196:3e59:e9ff
Info::
2 nameserver(s) configured
Got: ns1.dns-parking.com, ns2.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (348 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 348 ms
A88.222.222.117, 2.57.91.114
AAAA2a02:4780:84:306b:ccb:d06b:cc72:cfaa, 2a02:4780:84:be4f:752a:2196:3e59:e9ff
CNAME—
NSns1.dns-parking.com, ns2.dns-parking.com
MX
5 mx1.hostinger.com
10 mx2.hostinger.com
TXT
SPF v=spf1 include:_spf.mail.hostinger.com ~all
CAALookup not available with standard resolver
Resolved in 348 ms

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 23ms across 3 resolvers (spread 35ms)
PASS
Mean 23ms across 3 resolvers (spread 35ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Quad9: 39ms
Got: 39ms via 9.9.9.9:53
A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 65 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 65 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Sitemap: https://www.mcpl.ai/sitemap.xml

User-agent: *
Disallow:
sitemap.xml 200 OK
Type URL Set URLs 21 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
mcpl.ai — via GoDaddy.com, LLC, 1 years, 5 months old, hosted on Hostinger
PASS
mcpl.ai — via GoDaddy.com, LLC, 1 years, 5 months old, hosted on Hostinger
Info::
Domain registered until Apr 25, 2027 (7 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: GoDaddy.com, 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: Hostinger
Got: AS47583
Domain expiry

216 days

April 25, 2027

SSL certificate

62 days

Issued by Let's Encrypt

Domain age

1 years, 5 months

Registered April 25, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Hostinger

ASN AS47583

88.222.222.226

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC
Created April 25, 2025 (1 years, 5 months ago)
Expires April 25, 2027 (7 months)
Last Updated August 11, 2026
Name Servers ns1.dns-parking.com, ns2.dns-parking.com
DNSSEC Not enabled
Registrant Registration Private
Hosting
IP Address 88.222.222.226
ASN AS47583 (AS-HOSTINGER - Hostinger International Limited, CY)
Provider Hostinger
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 61 ms TCP Connect 24 ms TLS Handshake 31 ms Server Processing 25 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