Check public domain authority signals
Paste a domain to read HTTPS, on-page tags, robots.txt, Open PageRank, and archive history—not a proprietary Moz Domain Authority number.
Scan any domain for SEO trust signals — HTTPS, on-page tags, robots.txt, Open PageRank, and Wayback history.
Server-assisted scan — uses public data sources
Scan a domain
Enter a domain or homepage URL to estimate authority from public signals.
Public signals only
Open PageRank, robots.txt, sitemap hints, and homepage on-page SEO — no proprietary Moz/Ahrefs APIs.
Actionable breakdown
See which signals help or hurt your estimated score with per-factor detail.
Competitor research
Compare domains before outreach, guest posts, or link building.
What this scanner measures, and what it does not
People say domain authority when they mean a single vendor score from Moz or a similar link index. This page does not call Moz or Ahrefs. It gathers public signals and shows them with per-factor detail.
You enter example.com or a full homepage URL and press Scan domain. The output lists HTTPS status, title and meta description, H1 presence, robots.txt hints, sitemap hints, Open PageRank where available, and archive history cues.
The badge on the page marks the scan as server-assisted because it pulls public responses and published Open PageRank data rather than inventing a private link graph.
Why a public triage still helps
Before you buy a domain, pitch a guest post, or debug a thin site, you want a quick read of whether the homepage looks finished and crawlable. A missing title, a robots file that blocks everything, or an HTTP-only homepage shows up here without a paid SEO seat.
Open PageRank is one public popularity estimate. It is not identical to any commercial Domain Authority product. Treat it as one input beside the on-page and technical checks.
Use the factor list as a punch list. Fix crawl and HTTPS issues first. Popularity estimates move slowly on new hosts.
How to run a scan
Type the hostname or homepage address into the field. Press Scan domain. Wait for the server-assisted pass to finish, then read the factor list in the results panel.
Scan the live hostname you care about. A staging subdomain returns staging signals. A bare domain and a www host can differ if they are not aligned in DNS and redirects.
When comparing two domains for a partnership, scan both with the same method and compare the factor lists side by side rather than mixing vendor screenshots from different tools.
- Paste example.com or the full homepage URL for that host.
- Confirm you are evaluating production, not a staging name.
- Write down failing factors before you leave the results panel.
Reading weak HTTPS, tags, and robots results
No HTTPS, an empty title, or a robots file that blocks the whole site are concrete problems you can fix on the origin. The panel names those factors so you are not guessing from a single opaque score.
A low Open PageRank on a brand-new domain is ordinary. Age and links accumulate over time. Fix crawl and on-page issues first; popularity estimates follow later.
Missing meta description or H1 is an on-page gap you can correct in the CMS. Re-scan after deploy to confirm the public HTML changed.
Archive history as context, not a quality grade
Wayback-style history shows whether the hostname carried earlier sites. That context matters when you inherit a domain with a messy past or evaluate a seller’s story about a clean brand-new name.
History alone does not prove present quality. Pair it with the live homepage checks from the same scan: HTTPS, tags, and robots behavior today.
If archive snapshots show prior spam or unrelated niches, factor that into purchase and partnership decisions even when the live homepage looks finished.
What this tool is not
It is not a substitute for a full crawl of every URL. It is not a backlink index. It does not reveal proprietary Moz DA or Ahrefs Domain Rating numbers.
It does not change DNS, files, or rankings by itself. It reads public responses and datasets.
Use it as a fast public triage. Follow with Search Console and a proper crawler when you operate the site yourself.
After you scan
Write down the failing factors and fix them on the server or in the CMS. Re-scan the same hostname after deploy to confirm HTTPS, tags, and robots behave.
When the report is clean enough for your decision, save a screenshot or notes dated with the hostname. Domain sales and guest-post pitches move on evidence, not memory.
If you need a printable snapshot of a public page for an audit folder, convert that page layout to PDF on a separate tool after you finish the signal scan.
After you finish, open the result on your device, move keepers into a folder you control, and only then close this tab. That sequence keeps half-written files and lost downloads out of your next session.
If something fails, change one variable at a time: the input file or URL, the output format choice, or the network you are on. Note what changed so the next attempt is a measured test rather than a random retry.
Questions about domain authority checks
Is this the same as Moz Domain Authority?
No. Moz DA uses Moz’s link index. This page blends public signals such as Open PageRank with on-page and technical checks.
Do I need an SEO tool login?
No. The scan uses public data sources and does not require Moz, Ahrefs, or similar accounts.
What should I paste into the box?
Paste a bare domain like example.com or the full homepage URL. Use the exact host you want evaluated.
Why is Open PageRank missing or low?
New or lightly referenced domains often score low or lack a published value. Treat on-page and HTTPS findings as the actionable part of the report.
Does the scan change my site?
No. It reads public responses and datasets. It does not modify DNS, files, or rankings by itself.
Can I scan competitors?
Yes. Public homepage and robots data are visible to anyone. Use the results for research on public pages, not for accessing private systems.