How do I find out who hosts a website?

Paste the site URL into the lookup above. We resolve the domain to its IP address, identify the network owner (the hosting provider) and return their abuse contact. If the site hides behind a CDN such as Cloudflare, we tell you that too — the visible IP then belongs to the CDN, not the real host.

Where do I send a DMCA or abuse complaint for a website?

To the abuse mailbox of the hosting provider that physically serves the content. Complaints to the domain registrar are usually ignored — the registrar does not host the content. For large platforms (YouTube, Meta, Telegram) use their own report forms instead.

The site is behind Cloudflare — who do I complain to?

Cloudflare is a proxy, not the host. You can file through Cloudflare’s abuse form, which forwards the report to the real hosting provider and may disclose it. Getting the actual host to act usually takes a properly grounded notice and persistent follow-up — this is the step where most self-filed complaints stall.

What should the abuse email contain?

Identify the infringed work or right, the exact infringing URLs, your authority to act, a statement of good faith, and a clear removal request under the applicable statute (e.g. DMCA §512(c)(3)). Vague complaints are dropped; notices under a named statute get processed.

What if the hosting provider ignores the complaint?

Follow up on a schedule, escalate to the upstream network, and where appropriate pursue search de-indexing. Lawyerd runs this escalation ladder as a service — every notice filed by counsel, tracked until the content is actually gone.

Lawyerd · Free tool · Abuse-contact lookup

Find the abuse contact for any website.

Paste the address of the infringing site. We identify the hosting provider actually serving it and give you the abuse email your complaint should go to — not the registrar mailbox that ignores it.

Free and anonymous. Resolution runs live against DNS and network registries, cross-checked against contacts Lawyerd has used in real takedowns.

Complain to the host, not the registrar

Content lives on a server. The company that runs that server — the hosting provider — can remove it; the domain registrar generally cannot and will not. A takedown that works goes to the host’s abuse mailbox, under a named statute, with the exact URLs.

This lookup does three things: resolves the domain to its IP address, identifies the network that owns the IP (the hosting provider), and returns the abuse contact registered for that network. When the contact is one Lawyerd has already used in real filings, we mark it verified — mail to it is read and acted on.

If the site sits behind a CDN proxy such as Cloudflare, the visible IP belongs to the proxy and the real host is hidden. In that case the tool says so honestly — and where a previous Lawyerd case has already revealed the host behind that domain, we show the real contact instead. For the do-it-yourself route, see our guide on finding the real host behind Cloudflare; if a platform report already went nowhere, start with what to do when you reported it and nothing happened.

Questions filers actually ask

How do I find out who hosts a website?: Paste the site URL into the lookup above. We resolve the domain to its IP address, identify the network owner (the hosting provider) and return their abuse contact. If the site hides behind a CDN such as Cloudflare, we tell you that too — the visible IP then belongs to the CDN, not the real host.
Where do I send a DMCA or abuse complaint for a website?: To the abuse mailbox of the hosting provider that physically serves the content. Complaints to the domain registrar are usually ignored — the registrar does not host the content. For large platforms (YouTube, Meta, Telegram) use their own report forms instead.
The site is behind Cloudflare — who do I complain to?: Cloudflare is a proxy, not the host. You can file through Cloudflare’s abuse form, which forwards the report to the real hosting provider and may disclose it. Getting the actual host to act usually takes a properly grounded notice and persistent follow-up — this is the step where most self-filed complaints stall.
What should the abuse email contain?: Identify the infringed work or right, the exact infringing URLs, your authority to act, a statement of good faith, and a clear removal request under the applicable statute (e.g. DMCA §512(c)(3)). Vague complaints are dropped; notices under a named statute get processed.
What if the hosting provider ignores the complaint?: Follow up on a schedule, escalate to the upstream network, and where appropriate pursue search de-indexing. Lawyerd runs this escalation ladder as a service — every notice filed by counsel, tracked until the content is actually gone.

Hosting providers we have filed against

Abuse contacts confirmed through real takedown filings — including hosts that public WHOIS directories list wrong or not at all.

Or have it removed for you

Knowing the address is step one. Removal takes a notice under the right statute, follow-up on a schedule, and escalation when a host goes quiet. Lawyerd files under counsel and tracks every case until the content is verifiably gone.

Request removal by counsel

Building on top of this? The same resolution is available programmatically — request API access, or reach it today from any AI agent through our MCP endpoint.