Skip to content
https://kiostix.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 9 REVIEW
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 99.84.9.125 does not match any cert SAN: server-99-84-9-125.mad53.r.cloudfront.net
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 for 99.84.9.78 does not match any cert SAN: server-99-84-9-78.mad53.r.cloudfront.net
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 for 99.84.9.89 does not match any cert SAN: server-99-84-9-89.mad53.r.cloudfront.net
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 for 99.84.9.71 does not match any cert SAN: server-99-84-9-71.mad53.r.cloudfront.net
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

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

www / non-www

200https://www.kiostix.com/
200https://kiostix.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://kiostix.com/ → https://kiostix.com/

Consistent

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

Certificate validity

66
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
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
4 A records, 37 ms lookup
PASS
4 A records, 37 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 99.84.9.125, 99.84.9.78, 99.84.9.89, 99.84.9.71
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1629.awsdns-11.co.uk, ns-175.awsdns-21.com, ns-821.awsdns-38.net, ns-1188.awsdns-20.org
Info::
5 mail exchanger(s) configured
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 37 ms
Got: 37 ms
A99.84.9.125, 99.84.9.78, 99.84.9.89, 99.84.9.71
AAAA—
CNAME—
NSns-1629.awsdns-11.co.uk, ns-175.awsdns-21.com, ns-821.awsdns-38.net, ns-1188.awsdns-20.org
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=TioJU0XVed9XBkNAUUJU4XFS7oGh3DoAY40pjYt-Xls
CAALookup not available with standard resolver
Resolved in 37 ms

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)

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 35ms across 3 resolvers (spread 16ms)
PASS
Mean 35ms across 3 resolvers (spread 16ms)
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Quad9: 33ms
Got: 33ms via 9.9.9.9:53
Info::
Cloudflare: 44ms
Got: 44ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://kiostix.com

https://kiostix.com

9 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://kiostix.com2009 msHTTP/1.1
A
Domain Intelligence
kiostix.com — via GoDaddy.com, LLC, 15 years old, hosted on AWS
PASS
kiostix.com — via GoDaddy.com, LLC, 15 years old, hosted on AWS
Warning::
Domain expires in 77 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Feb 3, 2027
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: AWS
Got: AS16509
Domain expiry

72 days

February 3, 2027

SSL certificate

66 days

Issued by Amazon

Domain age

15 years

Registered February 3, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

99.84.9.71

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created February 3, 2012 (15 years ago)
Expires February 3, 2027 (2 months)
Last Updated February 3, 2025
Name Servers ns-1188.awsdns-20.org, ns-1629.awsdns-11.co.uk, ns-175.awsdns-21.com, ns-821.awsdns-38.net
DNSSEC Not enabled
Hosting
IP Address 99.84.9.71
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 613 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 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.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
613 ms
Total Time Total request time from DNS lookup through full response.
614 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 556 ms Content Transfer 1 ms
A
CDN & Delivery
Document and assets on AWS CloudFront
PASS
Document and assets on AWS CloudFront
Info::
Document is served via AWS CloudFront CDN (edge: MAD53-P8)
Got: x-amz-cf-id: JU1E0FnnHv4ZXSzYJiBW7zYwNnKoOaD_0hefg1hWAahnBPTVpvGMEQ==
Info::
CDN cache status: Miss from cloudfront
Info::
Assets on AWS CloudFront: staticassets.kiostix.com (assets: 38), cache Hit from cloudfront
Got: x-amz-cf-id: nXg9XXKb-PATu4Tmz8QgiPeHHl_jUSjj51EURSBlbmhI1L8ttVWwKQ==
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: JU1E0FnnHv4ZXSzYJiBW7zYwNnKoOaD_0hefg1hWAahnBPTVpvGMEQ==

Asset hosts on a CDN

  • staticassets.kiostix.com — AWS CloudFront · assets: 38 · Cache Status: Hit from cloudfront

Other asset hosts

  • tron.kiostix.com — assets: 10 · AWS
  • www.googletagmanager.com — assets: 3 · Google
  • cdn.jsdelivr.net — assets: 2 · below probe threshold
  • connect.facebook.net — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • unpkg.com — assets: 2 · below probe threshold
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Miss from cloudfront
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback