Skip to content
https://techydonut.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
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
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 193.58.105.55: lookup 193.58.105.55: 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 147.79.116.33: lookup 147.79.116.33: 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 2a02:4780:29:1f4c:3272:5cb6:b9a2:7804: lookup 2a02:4780:29:1f4c:3272:5cb6:b9a2:7804: 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 2a02:4780:2a:6b83:2124:6b48:e60:8a4c: lookup 2a02:4780:2a:6b83:2124:6b48:e60:8a4c: 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
Multi-Resolver DNS Speed
Mean 106ms across 3 resolvers (spread 134ms)
REVIEW
Mean 106ms across 3 resolvers (spread 134ms)
Info::
Quad9: 50ms
Got: 50ms via 9.9.9.9:53
Info::
Google: 85ms
Got: 85ms via 8.8.8.8:53
Info::
Cloudflare: 184ms
Got: 184ms via 1.1.1.1:53
B
TLS Certificate Expiry & Recommendations
49 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

49
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
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.
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: 500, /healthz: 500, /ping: 500, /status: 500.
A+
DNS Records
2 A records, 108 ms lookup
PASS
2 A records, 108 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 193.58.105.55, 147.79.116.33
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:4780:29:1f4c:3272:5cb6:b9a2:7804, 2a02:4780:2a:6b83:2124:6b48:e60:8a4c
Info::
2 nameserver(s) configured
Got: ns2.dns-parking.com, ns1.dns-parking.com
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'.
Info::
DNS resolution time: 108 ms
Got: 108 ms
A193.58.105.55, 147.79.116.33
AAAA2a02:4780:29:1f4c:3272:5cb6:b9a2:7804, 2a02:4780:2a:6b83:2124:6b48:e60:8a4c
CNAME—
NSns2.dns-parking.com, ns1.dns-parking.com
MX—
TXT
google-site-verification=mBt1aBzz_IQU3OwyW65BNRYJtYx_zmVutnR_CqNihq0
CAALookup not available with standard resolver
Resolved in 108 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://techydonut.com

https://techydonut.com

152 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://techydonut.com200152 msHTTP/1.1hcdn
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2a02:4780:29:1f4c:3272:5cb6:b9a2:7804, 2a02:4780:2a:6b83:2124:6b48:e60:8a4c
Got: 16 ms connect
IPv6 Ready
AAAA Records 2a02:4780:29:1f4c:3272:5cb6:b9a2:7804, 2a02:4780:2a:6b83:2124:6b48:e60:8a4c Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 36 URLs
PASS
robots.txt present, sitemap with 36 URLs
Info::
robots.txt is present
Got: 252 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 36 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 252 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
User-agent: *


Disallow: /cgi-bin/


Sitemap: https://techydonut.com/sitemap.xml

Sitemap: https://techydonut.com/sitemap_blog_posts.xml

Sitemap: https://techydonut.com/sitemap_blog_categories.xml

Sitemap: https://techydonut.com/images_sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 36 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: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.techydonut.com/
200https://techydonut.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
techydonut.com — via GoDaddy.com, LLC, 1 years, 4 months old
PASS
techydonut.com — via GoDaddy.com, LLC, 1 years, 4 months old
Info::
Domain registered until Jun 20, 2027 (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: 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.
Domain expiry

223 days

June 20, 2027

SSL certificate

49 days

Issued by Let's Encrypt

Domain age

1 years, 4 months

Registered June 20, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:4780:29:1f4c:3272:5cb6:b9a2:7804

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created June 20, 2025 (1 years, 4 months ago)
Expires June 20, 2027 (7 months)
Last Updated July 31, 2025
Name Servers ns1.dns-parking.com, ns2.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 2a02:4780:29:1f4c:3272:5cb6:b9a2:7804
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 90 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 134 ms Content Transfer 3 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback