Skip to content
https://dosebuddy-frontend.dosebuddy-health.workers.dev

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
8
PASS
8
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 8 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.166.161: lookup 172.67.166.161: 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.34.245: lookup 104.21.34.245: 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:3033::ac43:a6a1: lookup 2606:4700:3033::ac43:a6a1: 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:3036::6815:22f5: lookup 2606:4700:3036::6815:22f5: 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1248 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 1248 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a content-signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a content-signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a content signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via content signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

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::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

https://www.dosebuddy-frontend.dosebuddy-health.workers.dev/
200https://dosebuddy-frontend.dosebuddy-health.workers.dev/

HTTP → HTTPS

200http://dosebuddy-frontend.dosebuddy-health.workers.dev/

HTTP version does not redirect to HTTPS

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

Certificate validity

78
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, 50 ms lookup
PASS
2 A records, 50 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.166.161, 104.21.34.245
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3033::ac43:a6a1, 2606:4700:3036::6815:22f5
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'.
Info::
DNS resolution time: 50 ms
Got: 50 ms
A172.67.166.161, 104.21.34.245
AAAA2606:4700:3033::ac43:a6a1, 2606:4700:3036::6815:22f5
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 50 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 24ms across 3 resolvers (spread 17ms)
PASS
Mean 24ms across 3 resolvers (spread 17ms)
Info::
Quad9: 14ms
Got: 14ms via 9.9.9.9:53
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
Info::
Cloudflare: 31ms
Got: 31ms 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://dosebuddy-frontend.dosebuddy-health.workers.dev

https://dosebuddy-frontend.dosebuddy-hea...

120 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dosebuddy-frontend.dosebuddy-hea...200120 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3033::ac43:a6a1, 2606:4700:3036::6815:22f5
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3033::ac43:a6a1, 2606:4700:3036::6815:22f5 Connection Reachable (17 ms)
A+
HTTP Probe Timing
Total 195 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
44 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
32 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
194 ms
Total Time Total request time from DNS lookup through full response.
196 ms

Connection waterfall

DNS Lookup 44 ms TCP Connect 16 ms TLS Handshake 32 ms Server Processing 101 ms Content Transfer 2 ms
A+
CDN & Delivery
Document on Cloudflare Workers; assets also on Cloudflare
PASS
Document on Cloudflare Workers; assets also on Cloudflare
Info::
Document is served via Cloudflare Workers CDN
Got: delegation dosebuddy-frontend.dosebuddy-health.workers.dev
Info::
CDN cache status: HIT
Info::
Assets on Cloudflare: cdn.jsdelivr.net (assets: 3), cache HIT
Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net
Document served via CDN: Cloudflare Workers
Provider Cloudflare Workers Cache Status HIT Evidence delegation dosebuddy-frontend.dosebuddy-health.workers.dev

Asset hosts on a CDN

  • cdn.jsdelivr.net — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • flagcdn.com — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=HIT
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback