Enter a domain, URL, IP, email, or record and get a focused result without setup.
Hreflang checker
Enter a page URL to validate its hreflang tags and confirm that alternate language pages link back to it.
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at these companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Language and region codes are checked, including en-UK and underscore mistakes.
Alternate pages are fetched to confirm they reference the audited page.
Annotations in the HTTP Link header are read as well as link tags in the HTML.
Example request
GET /v1/hreflang?url=example.com
GET /v1/hreflang?url=example.com/en/&max_alternates=20
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently asked questions
It is recommended. x-default tells search engines which page to show when no language or region matches the visitor.
Yes. Each page should include a self-referencing entry along with every alternate version.
Up to 10 by default and up to 20 through the API. Alternates that cannot be read are reported as unknown.

