Skip to content
https://www.asetka.org/index.shtml

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 365ms across 3 resolvers (spread 964ms)
FIX
Mean 365ms across 3 resolvers (spread 964ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 92ms
Got: 92ms via 9.9.9.9:53
Info::
Cloudflare: 984ms
Got: 984ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 964ms (min 20ms / max 984ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 2117 ms lookup
REVIEW
1 A records, 2117 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 205.196.219.79
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (2117 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 2117 ms
A205.196.219.79
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 2117 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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 205.196.219.79 does not match any cert SAN: apache2-fritz.pdx1-shared-a2-05.dreamhost.com
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
50 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

50
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
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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.asetka.org/index.shtml

https://www.asetka.org/index.shtml

530 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.asetka.org/index.shtml200530 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 121 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 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 121 B Sitemaps referenced 0 User-agents *, ia_archiver Blocking No — crawling allowed
# Robots Access for AsetKa.org - Kemetic Order of Aset Ka

User-agent: *

Allow: /


User-agent: ia_archiver
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 14 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: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.asetka.org/index.shtml
301https://asetka.org/index.shtml

Preferred variant: www

Trailing Slash

302https://www.asetka.org/index.shtml/
200https://www.asetka.org/index.shtml

HTTP → HTTPS

301http://www.asetka.org/index.shtml → https://www.asetka.org/index.shtml

Consistent

A+
Domain Intelligence
asetka.org — via DreamHost, LLC, 20 years, 11 months old, hosted on DREAMHOST-AS - New Dream Network, LLC, US
PASS
asetka.org — via DreamHost, LLC, 20 years, 11 months old, hosted on DREAMHOST-AS - New Dream Network, LLC, US
Info::
Domain registered until Feb 28, 2027 (4 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: DreamHost, 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: DREAMHOST-AS - New Dream Network, LLC, US
Got: AS26347
Domain expiry

125 days

February 28, 2027

SSL certificate

50 days

Issued by Let's Encrypt

Domain age

20 years, 11 months

Registered February 28, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DREAMHOST-AS - New Dream Network, LLC, US

ASN AS26347

205.196.219.79

Registrar

DreamHost, LLC

Unlocked 3 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 DreamHost, LLC
Created February 28, 2006 (20 years, 11 months ago)
Expires February 28, 2027 (4 months)
Last Updated August 12, 2026
Name Servers khufu.asetka.org, khafre.asetka.org, menkaure.asetka.org
DNSSEC Not enabled
Hosting
IP Address 205.196.219.79
ASN AS26347 (DREAMHOST-AS - New Dream Network, LLC, US)
Provider DREAMHOST-AS - New Dream Network, LLC, US
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 113 ms TCP Connect 162 ms TLS Handshake 166 ms Server Processing 349 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://www.asetka.org/health (HTTP 200)
PASS
Health endpoint at https://www.asetka.org/health (HTTP 200)
Info::
Public health endpoint at https://www.asetka.org/health
Got: https://www.asetka.org/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback