Skip to content
https://tomdawayhet.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
10
PASS
5
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
5 PASS 10 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2a00:4b40:aaaa:2004::7
Info::
IPv6 connection error
Got: dial tcp6 [2a00:4b40:aaaa:2004::7]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a00:4b40:aaaa:2004::7 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 37.9.175.156 does not match any cert SAN: ing.r2.websupport.sk
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 lookup failed for 2a00:4b40:aaaa:2004::7: lookup 2a00:4b40:aaaa:2004::7: 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 148ms across 3 resolvers (spread 156ms)
REVIEW
Mean 148ms across 3 resolvers (spread 156ms)
Info::
Cloudflare: 71ms
Got: 71ms via 1.1.1.1:53
Info::
Quad9: 148ms
Got: 148ms via 9.9.9.9:53
Info::
Google: 227ms
Got: 227ms via 8.8.8.8:53
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.tomdawayhet.com/
200https://tomdawayhet.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
HTTP Probe Timing
Total 1150 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
209 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
173 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
183 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.13 s
Total Time Total request time from DNS lookup through full response.
1.15 s

Connection waterfall

DNS Lookup 209 ms TCP Connect 173 ms TLS Handshake 183 ms Server Processing 568 ms Content Transfer 17 ms
B
TLS Certificate Expiry & Recommendations
73 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

73
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.
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
1 A records, 197 ms lookup
PASS
1 A records, 197 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 37.9.175.156
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: 2a00:4b40:aaaa:2004::7
Info::
3 nameserver(s) configured
Got: ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 197 ms
Got: 197 ms
A37.9.175.156
AAAA2a00:4b40:aaaa:2004::7
CNAME—
NSns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk
MX
10 mailin1.tomdawayhet.com
100 mailin2.tomdawayhet.com
TXT
SPF v=spf1 a mx include:_spf.m1.websupport.sk ?all
spf2.0/pra a mx include:_sid.m1.websupport.sk ?all
google-site-verification=1dXR_p48m6nRcPqziJTkaQjvATy4a95BAXTASpdIizY
CAALookup not available with standard resolver
Resolved in 197 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

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://tomdawayhet.com

https://tomdawayhet.com

683 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tomdawayhet.com200683 msHTTP/1.1openresty
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 59 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 59 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Sitemap: https://tomdawayhet.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 3 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
tomdawayhet.com — via Gransy, s.r.o., 6 years, 9 months old, hosted on WEBSUPPORT-SRO-SK-AS - WebSupport s.r.o., SK
PASS
tomdawayhet.com — via Gransy, s.r.o., 6 years, 9 months old, hosted on WEBSUPPORT-SRO-SK-AS - WebSupport s.r.o., SK
Info::
Domain registered until Dec 9, 2026 (3 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: Gransy, s.r.o.
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: WEBSUPPORT-SRO-SK-AS - WebSupport s.r.o., SK
Got: AS51013
Domain expiry

113 days

December 9, 2026

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

6 years, 9 months

Registered December 9, 2019

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WEBSUPPORT-SRO-SK-AS - WebSupport s.r.o., SK

ASN AS51013

37.9.175.156

Registrar

Gransy, s.r.o.

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 Gransy, s.r.o.
Created December 9, 2019 (6 years, 9 months ago)
Expires December 9, 2026 (3 months)
Last Updated December 17, 2025
Name Servers ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk
DNSSEC Not enabled
Hosting
IP Address 37.9.175.156
ASN AS51013 (WEBSUPPORT-SRO-SK-AS - WebSupport s.r.o., SK)
Provider WEBSUPPORT-SRO-SK-AS - WebSupport s.r.o., SK
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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback