hosting_verifyDomainOwnershipV1

Verify ownership of a single domain and return the verification status. Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have is_accessible: true. If not, add the given TXT record to your domain's DNS rec...

SERVERHostinger Api SOURCEhostinger-api-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-verifydomainownershipv1.md

What hosting_verifyDomainOwnershipV1 does on Hostinger Api

AI agents call hosting_verifyDomainOwnershipV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
domain string Yes Domain to verify ownership for

Parameters from the server's own tool schema.

Why hosting_verifyDomainOwnershipV1 is rated Low

This tool retrieves and validates domain ownership information without modifying, deleting, or executing operations. It is purely informational—checking accessibility and returning a verification status. No data is created, modified, or deleted. No financial transactions or destructive operations occur.

From the tool's definition Tool checks/queries domain ownership verification status and returns `is_accessible` boolean. Actions are read-only queries with no side effects: 'check if a domain is accessible', 'return the verification status'.

Questions about hosting_verifyDomainOwnershipV1

What does the hosting_verifyDomainOwnershipV1 tool do? +

Verify ownership of a single domain and return the verification status. Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have is_accessible: true. If not, add the given TXT record to your domain's DNS records and try verifying again. Keep in mind that it may take up to 10 minutes for new TXT DNS records to propagate. Skip this verification when using Hostinger's free subdomains (*.hostingersite.com). It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does hosting_verifyDomainOwnershipV1 accept? +

hosting_verifyDomainOwnershipV1 accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_verifyDomainOwnershipV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_verifyDomainOwnershipV1: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Hostinger Api. Nothing to install.

What risk level is hosting_verifyDomainOwnershipV1? +

hosting_verifyDomainOwnershipV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hosting_verifyDomainOwnershipV1? +

Yes. Add a rate_limit block to the hosting_verifyDomainOwnershipV1 rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block hosting_verifyDomainOwnershipV1 completely? +

Set action: deny in the PolicyLayer policy for hosting_verifyDomainOwnershipV1. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides hosting_verifyDomainOwnershipV1? +

hosting_verifyDomainOwnershipV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Hostinger Api, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.