Domain report
Enter a domain and get one scored report that brings together its registration, DNS, web security, hosting and email setup, with a link to the full tool behind every part.
Results for wikipedia.org
Domain report
In very good shape: 92 out of 100
In very good shape.
Weighted over the areas we could read.
Registered 25 years ago and paid up for 2 months.
Good- Each section is read live or from the stored copy of its own tool, so it may be a few minutes old. Open a section for the full tool.
Registration2
Good 92 out of 100
Registered 25 years ago and paid up for 2 months.
- Registration ends in 60 days.
- A transfer lock is on, which makes hijacking by transfer harder.
- Registrar
- MarkMonitor Inc.
- Registered
- 2001-01-13
- Expires
- 2027-01-13
- Age
- 25 years
What we ran
- Registration record: looked up now
Structured result (JSON) · 1.3 KB
{
"domain": "wikipedia.org",
"registrable": "wikipedia.org",
"score": 92,
"rating": "excellent",
"summary": "In very good shape.",
"areas": [
{
"id": "registration",
"title": "Registration",
"parts": [
{
"tool": "whois-lookup",
"label": "Registration record",
"href": "/whois?q=wikipedia.org",
"status": "ok",
"cache": "miss"
}
],
"status": "good",
"score": 92,
"headline": "Registered 25 years ago and paid up for 2 months.",
"facts": [
{
"label": "Registrar",
"value": "MarkMonitor Inc."
},
{
"label": "Registered",
"value": "2001-01-13"
},
{
"label": "Expires",
"value": "2027-01-13"
},
{
"label": "Age",
"value": "25 years"
}
],
"findings": [
{
"severity": "info",
"text": "Registration ends in 60 days."
},
{
"severity": "good",
"text": "A transfer lock is on, which makes hijacking by transfer harder."
}
]
}
],
"notes": [
"Each section is read live or from the stored copy of its own tool, so it may be a few minutes old. Open a section for the full tool."
]
}What the domain report does
Most questions about a domain start the same way. Who owns it, is it set up properly, and is anything about to break? Answering them usually means opening five or six tools in a row. The domain report runs those checks together and puts the results on one page, so you can see in a minute where a domain is solid and where it needs work.
It does not do any new kind of lookup. Behind each section sits one of the tools on this site: the WHOIS lookup, the DNS lookup, the SSL checker, the security headers checker, the hosting finder and the checkers for SPF, DMARC, DKIM and blocklists. The report asks each one, reads the answer and turns it into a score and a plain sentence.
Because every part is the real tool, nothing is hidden. Each section links to the full result for the same domain, so you can open the details behind any score and check our working.
How to use it
- Enter a domainType
example.com, or paste a web address or an email address and we will reduce it to the domain. IP addresses are not accepted here, because a domain report is about a name. For an address, try the IP lookup. - Read the summary firstThe top of the report shows an overall score and one tile for each area, each with its own score and a one-line verdict. Anything below 65 is worth a look.
- Open the area that needs workThe tabs below list the findings, the key facts and which parts ran. Follow the link in a tab to the full tool for that part, with the domain already filled in.
Under More options you can switch sections off. Email is the largest part by far, because it runs four checkers and asks several blocklists about the mail servers. If you only care about registration and DNS, leave the others out and the report is quicker and costs less of your allowance.
# The same report as JSON
curl "https://lookupowl.com/api/v1/tools/domain-report?domain=example.com"How the scores work
Each scored area starts at 100 and loses points for specific, named problems. The overall score is a weighted average of the areas that could be read. Hosting is shown for information and is not scored, because there is no wrong host.
| Area | Weight | What lowers the score |
|---|---|---|
| Registration | 20 | A hold on the domain, a grace period, redemption or pending delete, expiry within 90 days, a very new registration |
| DNS | 20 | No or only one nameserver, a missing SOA, no address, a resolver error, DNSSEC not validating, a name that does not exist |
| Web security | 30 | An expired, untrusted or mismatched certificate; the security headers score from the headers checker. The two are averaged |
| 30 | SPF (25), DMARC (35), DKIM (15) and blocklists (25), counted among the parts that answered | |
| Hosting | not scored | Nothing. It names the host or CDN, the DNS provider and the email provider |
A part that fails, for example a mail server that does not answer in time, is marked as failed and left out of the average. It is never counted as zero, and the summary says which part is missing. The overall score reads as excellent from 85, good from 70, in need of attention from 50 and poor below that.
What it does not do
- It does not find hidden servers. When a CDN answers for a site, the report says the origin is hidden and stops there.
- It does not scan ports, crawl the site or test for vulnerabilities. It reads public records and makes one connection to the site for the certificate and one request for the headers.
- It is a snapshot, not monitoring. Run it again after you change something, or after the cache lifetime of the individual checks has passed.
- It cannot see private settings, such as how a mail provider filters inbound mail. The email score is about what the domain publishes.
DKIM is the one email check that can miss something. Selectors cannot be listed, so the report tries the common ones. Finding none is shown as "not proof", and it counts for less than a record that is clearly missing.
Questions people ask
How long does a domain report take?
Usually 5 to 15 seconds, because the sections run at the same time and the slowest one sets the pace. Mail server blocklists are normally the slowest. If a section is not finished after about 24 seconds, the report shows what it has and marks that section.
Why does a report cost more than one lookup?
It runs up to nine checks in one go, so it uses more of your free allowance than a single tool. A full report counts for about 60 units, which is the most any one request can use. Choosing fewer sections lowers the price, and registration and DNS alone are cheap.
What if one section fails?
The rest of the report still arrives. The failed section says what went wrong, usually a timeout or a server that did not answer, and it is left out of the score instead of counting as zero. Run the report again in a minute and it often fills in.
Can I run it on a subdomain?
Yes. DNS, the certificate, the security headers and hosting are read for the subdomain you enter. Registration and email belong to the main domain, so those are read for it, and the report tells you so.
Is a high score a guarantee that a domain is safe?
No. The score tells you how well the domain is set up on the points we can check from outside. A phishing domain can have a valid certificate, strong headers and a perfect mail setup. Treat the registration age and the findings as clues, not a verdict on the owner.
Do you store the domains I check?
Results are kept for a short time so repeat requests are quick. Our privacy page says exactly what is stored and what is sent to our analytics service.
Can an AI assistant run this report?
Yes. The same report is the domain_report tool on the LookupOwl MCP server at https://lookupowl.com/mcp. It returns the scores, findings and links as structured data, which suits an assistant that has to explain a domain in a sentence or two.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is domain_report. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/domain-report?q=example.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp