Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
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)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations87 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 32 ms lookupPASS
| A | 172.67.188.16, 104.21.7.219 |
| AAAA | 2606:4700:3030::6815:7db, 2606:4700:3031::ac43:bc10 |
| CNAME | — |
| NS | andronicus.ns.cloudflare.com, isabel.ns.cloudflare.com |
| MX | 24 route2.mx.cloudflare.net 26 route1.mx.cloudflare.net 49 route3.mx.cloudflare.net |
| TXT | google-site-verification=XcEKRgQbz6w7zbinsKPbPuuQul49KUkXCzpdvulEyVg SPF v=spf1 include:_spf.mx.cloudflare.net ~all yandex-verification: 98ea68545d1594d8 |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 11ms across 3 resolvers (spread 12ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://bazicalculator.pro
109 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bazicalculator.pro | 200 | 109 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 448 URLsPASS
User-Agent: *
Allow: /
Disallow: /api/*
Disallow: /_next/*
Disallow: /settings/*
Disallow: /dashboard/*
Host: bazicalculator.pro
Sitemap: https://bazicalculator.pro/sitemap.xml
# LLM brief: https://bazicalculator.pro/llms.txt
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebazicalculator.pro — via NameCheap, Inc., 2 days oldPASS
361 days
October 15, 2027
87 days
Issued by Google Trust Services
2 days
Registered October 15, 2026
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3031::ac43:bc10
NameCheap, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Newly registered domain — build backlinks and content to establish SEO trust
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
Informational: domain age. Newer domains may have lower trust signals in spam/security filters.
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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