Skip to content
https://akkadia.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
5 PASS 3 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 52 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 52 B Sitemaps referenced 0 User-agents * Disallow: / User-agent: * Blocking No — crawling allowed
User-agent: *
Disallow: /
User-agent: *
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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 301-redirects to HTTPS

www / non-www

200https://www.akkadia.org/
200https://akkadia.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://akkadia.org/ https://akkadia.org/

Consistent

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

Certificate validity

38
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 DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 160 ms lookup
PASS
1 A records, 160 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 94.16.121.6
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: 2a03:4000:21:111::
Info::
2 nameserver(s) configured
Got: ns2.hover.com, ns1.hover.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 160 ms
Got: 160 ms
A94.16.121.6
AAAA2a03:4000:21:111::
CNAME
NSns2.hover.com, ns1.hover.com
MX
1 smtp.akkadia.org
TXT
SPF v=spf1 ip4:45.83.107.222 ip6:2a03:4000:46:5de:8463:f3ff:fe06:bcd2 -all
CAALookup not available with standard resolver
Resolved in 160 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://akkadia.org

https://akkadia.org

120 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://akkadia.org200120 msHTTP/1.1Apache/2.4.66 (Fedora Linux) OpenSSL/3.5.4
A+
IPv6 Readiness
IPv6 reachable (2052 ms)
PASS
IPv6 reachable (2052 ms)
Info::
IPv6 is configured and reachable at 2a03:4000:21:111::
Got: 2052 ms connect
IPv6 Ready
AAAA Records 2a03:4000:21:111:: Connection Reachable (2052 ms)
A+
Domain Intelligence
akkadia.org — via Tucows Domains Inc., 24 years, 9 months old
PASS
akkadia.org — via Tucows Domains Inc., 24 years, 9 months old
Info::
Domain registered until Nov 20, 2027 (1 years, 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: Tucows Domains Inc.
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

522 days

November 20, 2027

SSL certificate

38 days

Issued by Let's Encrypt

Domain age

24 years, 9 months

Registered November 20, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a03:4000:21:111::

Registrar

Tucows Domains Inc.

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 Tucows Domains Inc.
Created November 20, 2001 (24 years, 9 months ago)
Expires November 20, 2027 (1 years, 7 months)
Last Updated October 25, 2022
Name Servers ns1.hover.com, ns2.hover.com
DNSSEC Not enabled
Hosting
IP Address 2a03:4000:21:111::
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 151 ms TCP Connect 39 ms TLS Handshake 43 ms Server Processing 39 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