Domain Report
Free, no signup. One bounded check for the public signals around a domain: DNS, registry data, hosting, reachability, and safety. Every section keeps its evidence and its focused-tool handoff.
Sample report
Illustrative example — fixed module states using the real roll-up formula
- DNS: Pass
- Whois / RDAP: Needs attention
- Hosting: Not evaluated
- Availability: Pass
- Safety: Needs attention
Two warnings · one not evaluated. The missing hosting check contributes zero and remains visible; it is not treated as a pass.
How to use it
- Enter a root domain.
- Run the report, then read every module state before the overall score.
- Expand evidence and open the focused handoff for any warning, error, or not-evaluated module.
- Download a summary card or print only after reviewing the point-in-time caveat.
Current target
Recent checks appear below. Use the star beside any saved site, page, or list to favorite it.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
This report combines bounded public checks at one point in time. A passing section is not proof that a service is healthy, secure, authoritative, or free of hidden configuration problems.
Rate this tool
What the results mean
- Pass means that bounded module observed no implemented error.
- Needs attention means the evidence contains a warning.
- Errors means a defined adverse condition was observed.
- Not evaluated means the service or request did not supply usable evidence.
The average uses pass 100, warning 60, errors 0, and not evaluated 0. It is an orientation score, not a domain-health standard.
How it works
One request runs five bounded modules: public DNS, registry RDAP, hosting evidence, one-location availability, and public website-safety signals. Each module returns its own state, summary, and evidence so partial failures remain isolated. The browser calculates the transparent roll-up and links every module to its focused tool.
Features
- Five public-signal checks in one request.
- Partial-result handling with explicit not-evaluated states.
- Evidence drawers and prefilled focused-tool handoffs.
- Downloadable result card and print/PDF layout.
Limitations
This is not authoritative DNS, registrar account access, origin discovery, continuous uptime monitoring, a penetration test, or full safety assessment. A CDN can hide the origin; registry data can be redacted; external services can be unavailable; and every result is a point-in-time public view.
Frequently asked questions
Does this reveal my origin server?
No. A CDN or reverse proxyA CDN (content delivery network) is a geographically distributed network of edge servers that caches and serves your content from a location close to each visitor and crawler. It isn't a ranking factor itself, but it affects things Google and Bing do use — page speed and Core Web Vitals, crawl efficiency, uptime, and HTTPS delivery — and, if misconfigured, can block crawlers or muddle canonicalization. can deliberately hide an origin. The hosting section reports only public DNS, network, and response-header evidence.
Why is a section marked not evaluated?
Each section relies on a different public service or bounded web request. If one cannot complete, the report keeps that section visible as not evaluated instead of implying a pass or leaving a blank result.
Is this an uptime monitor or security scan?
No. Availability is a point-in-time check from one Cloudflare location, and safety is a public-signal snapshot. Neither replaces monitoring, a penetration test, or incident response.
How is the overall domain score calculated?
Each of five modules contributes 100 for pass, 60 for warning, and 0 for errors or not evaluated, then the values are averaged. Because unavailable evidence scores zero, always read module states instead of using the score alone.
Can I use this report as proof of domain health?
No. It is an orientation report built from bounded public checks at one point in time. Open the focused tools and your provider accounts for authoritative diagnosis.
Feature requests for Domain Report
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Common issues & how to fix them
- Errors DNS section failed Fix: Repair the domain’s delegation or authoritative DNS response, then rerun the report after propagation.
- Errors Registration status needs attention Fix: Review the flagged RDAP status with the registrar and renew, unlock, or correct registration data as appropriate.
- Warnings Origin host is not identified Fix: Confirm the origin using your DNS/CDN configuration or hosting account because public signals do not identify it reliably.
- Errors Availability section failed Fix: Restore a reachable HTTPS response at the checked host and resolve any DNS, TLS, timeout, or origin error.
- Errors Safety section failed Fix: Investigate the named safety signal, remove compromised or deceptive content, and request review from the relevant provider.