Skip to content
https://akj.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
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.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 76.76.21.21: lookup 76.76.21.21: 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.
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
HTTP Probe Timing
Total 1325 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
40 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.24 s
Total Time Total request time from DNS lookup through full response.
1.33 s

Connection waterfall

DNS Lookup 46 ms TCP Connect 1 ms TLS Handshake 40 ms Server Processing 1.15 s Content Transfer 84 ms
B
TLS Certificate Expiry & Recommendations
38 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
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
1 A records, 266 ms lookup
PASS
1 A records, 266 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 76.76.21.21
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: hugh.ns.cloudflare.com, lily.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (266 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 266 ms
A76.76.21.21
AAAA—
CNAME—
NShugh.ns.cloudflare.com, lily.ns.cloudflare.com
MX
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com
TXT
brave-ledger-verification=fd4c1a12756560ca02dfa1f739d4cc73347e99ea123b5ee178db4c...
google-site-verification=XYmtFep4gnaHlmYiZjz78BcFbYdi-72ZNckAqHW0WCI
SPF v=spf1 include:spf.messagingengine.com ?all
keybase-site-verification=dgHya9LcjI39b2A27AG16GP__K-OGQc19bTapn9EwjE
have-i-been-pwned-verification=ee892164660d33de8789aa79ea7e31d6
CAALookup not available with standard resolver
Resolved in 266 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

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+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Multi-Resolver DNS Speed
Mean 24ms across 3 resolvers (spread 43ms)
PASS
Mean 24ms across 3 resolvers (spread 43ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 27ms
Got: 27ms via 1.1.1.1:53
Info::
Google: 44ms
Got: 44ms 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://akj.io

https://akj.io

1617 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://akj.io2001617 msHTTP/1.1Vercel
A+
Crawlability
robots.txt present, sitemap with 20 URLs
PASS
robots.txt present, sitemap with 20 URLs
Info::
robots.txt is present
Got: 94 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 94 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robotstxt.org/
User-agent: *
Content-Signal: search=yes, ai-train=no, ai-input=yes
Allow: /

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 308

www / non-www

https://www.akj.io/
200https://akj.io/

HTTP → HTTPS

308http://akj.io/ → https://akj.io/

Consistent

A+
Domain Intelligence
akj.io — via 101domain GRS Limited, 11 years, 11 months old, hosted on AWS
PASS
akj.io — via 101domain GRS Limited, 11 years, 11 months old, hosted on AWS
Info::
Domain registered until Jan 15, 2028 (1 years, 2 months remaining)
Info::
Registrar: 101domain GRS Limited
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

444 days

January 15, 2028

SSL certificate

38 days

Issued by Let's Encrypt

Domain age

11 years, 11 months

Registered January 15, 2015

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

101domain GRS Limited

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 101domain GRS Limited
Created January 15, 2015 (11 years, 11 months ago)
Expires January 15, 2028 (1 years, 2 months)
Last Updated August 11, 2026
Name Servers hugh.ns.cloudflare.com, lily.ns.cloudflare.com
Registrant Digital Privacy Corporation
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.5s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
CDN & Delivery
Vercel (MISS)
PASS
Vercel (MISS)
Info::
Document is served via Vercel CDN
Got: x-vercel-id: cdg1::iad1::5hfgn-1793111079014-c5b0651242f9
Info::
CDN cache status: MISS
Document served via CDN: Vercel
Provider Vercel Cache Status MISS Evidence x-vercel-id: cdg1::iad1::5hfgn-1793111079014-c5b0651242f9
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 2 header(s)
Got: age=0, x-vercel-cache=MISS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback