Skip to content
https://kirkify.cc

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
17
10 PASS 7 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.217.45: lookup 172.67.217.45: 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.
Info::
PTR lookup failed for 104.21.86.85: lookup 104.21.86.85: 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.
Info::
PTR lookup failed for 2606:4700:3032::6815:5655: lookup 2606:4700:3032::6815:5655: 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.
Info::
PTR lookup failed for 2606:4700:3037::ac43:d92d: lookup 2606:4700:3037::ac43:d92d: 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.
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 308

www / non-www

200https://www.kirkify.cc/
200https://kirkify.cc/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://kirkify.cc/ → https://www.kirkify.cc/

Consistent

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

Certificate validity

60
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
2 A records, 41 ms lookup
PASS
2 A records, 41 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.217.45, 104.21.86.85
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3032::6815:5655, 2606:4700:3037::ac43:d92d
Info::
2 nameserver(s) configured
Got: terry.ns.cloudflare.com, irena.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 41 ms
Got: 41 ms
A172.67.217.45, 104.21.86.85
AAAA2606:4700:3032::6815:5655, 2606:4700:3037::ac43:d92d
CNAME—
NSterry.ns.cloudflare.com, irena.ns.cloudflare.com
MX
1 route2.mx.cloudflare.net
23 route3.mx.cloudflare.net
70 route1.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
google-site-verification=YEi8C0uNOzY9e0Hv4H5m710ZD989AcGcUOUoPG3xH2Q
CAALookup not available with standard resolver
Resolved in 41 ms
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 39ms across 3 resolvers (spread 24ms)
PASS
Mean 39ms across 3 resolvers (spread 24ms)
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Cloudflare: 38ms
Got: 38ms via 1.1.1.1:53
Info::
Quad9: 52ms
Got: 52ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 537 ms total
PASS
1 redirect(s), 537 ms total
Info::
Single redirect
Got: https://kirkify.cc → https://www.kirkify.cc/ (308)
Info::
WWW normalization redirect
Info::
Redirect overhead: 537 ms total
Got: 537 ms

https://kirkify.cc

122 ms · HTTP/1.1

308

https://www.kirkify.cc/

416 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://kirkify.cc308122 msHTTP/1.1cloudflare
2https://www.kirkify.cc/200416 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3032::6815:5655, 2606:4700:3037::ac43:d92d
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3032::6815:5655, 2606:4700:3037::ac43:d92d Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 29 URLs
PASS
robots.txt present, sitemap with 29 URLs
Info::
robots.txt is present
Got: 266 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 29 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 266 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /*?*q=
Disallow: /settings/*
Disallow: /activity/*
Disallow: /admin/*
Disallow: /api/*
Disallow: /zh/settings/*
Disallow: /zh/activity/*
Disallow: /zh/admin/*

Host: https://www.kirkify.cc
Sitemap: https://www.kirkify.cc/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 29 entries Valid XML Yes
Sample URLs:
A
Domain Intelligence
kirkify.cc — via Spaceship, Inc., 10 months old
PASS
kirkify.cc — via Spaceship, Inc., 10 months old
Warning::
Domain expires in 40 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Nov 25, 2026
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: Spaceship, 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

37 days

November 25, 2026

SSL certificate

60 days

Issued by Google Trust Services

Domain age

10 months

Registered November 25, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3037::ac43:d92d

Registrar

Spaceship, Inc.

Unlocked 2 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 Spaceship, Inc.
Created November 25, 2025 (10 months ago)
Expires November 25, 2026 (1 months)
Last Updated November 26, 2025
Name Servers irena.ns.cloudflare.com, terry.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3037::ac43:d92d
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 43 ms TCP Connect 17 ms TLS Handshake 29 ms Server Processing 62 ms Content Transfer 0 ms
A
CDN & Delivery
Document and assets on Cloudflare
PASS
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a4b5e8bbcedac9c2-CDG
Info::
CDN cache status: DYNAMIC
Info::
Assets on Cloudflare: www.kirkify.cc (assets: 26), cache DYNAMIC
Got: cf-ray: a4b5ea30dce3f158-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a4b5e8bbcedac9c2-CDG

Asset hosts on a CDN

  • www.kirkify.cc — Cloudflare · assets: 26 · Cache Status: DYNAMIC

Other asset hosts

  • analytics.transcribevideototext.io — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback