How to check if a delisted link is still in bing.com results
Verifying a bing.com removal means searching the exact URL and then the terms it ranked for, because a grant can be narrower than the request. Checking only one engine is also how creators conclude a removal worked while the other index continues returning the same page.
Left up, 90 exposed copies work out to an estimated $526 a month in diverted subscriptions. Estimate, not a measurement: it assumes 0.45 diverted subscribers per exposed post at an average subscription price of $12.99. Your number depends on your pricing and audience.
Removal route for bing.com
Resolved live · no account · nothing uploaded
bing.com is an index, not a host. Delisting is the whole route.
1 · Curated host route— silent.No host_handlers row for bing.com.
2 · RDAP abuse contact— resolves.abusecomplaints@markmonitor.com — the registrar's abuse desk, not bing.com itself. Probed 2026-09-04.
3 · Fallback address— not needed.Not needed — an earlier rung resolved.
4 · Network and search— resolves.Delisting is the route here — the index holds the result, not the file.
What happens to what you type: nothing. The domain is matched against openDMCA's routing table in your browser. No request is made to bing.com, no page is fetched, and the text is not stored or sent anywhere.
Search the exact URL on bing.com. Query the full URL. A result means the index still holds it, regardless of what the request status reports, and that is the direct evidence available from outside.
Search the terms that surfaced it. Run your stage name and the other queries that returned the page on bing.com. A grant against one query can leave the page returning for another.
Check the engines that draw on this index. Other search products use the bing.com index. Checking one of them shows whether the removal propagated beyond the engine you filed with.
Check image results as well. Image results have their own queue. A cleared web result on bing.com with a live thumbnail still returns for a name search.
Record the outcome against the request. Tie each verified URL back to the request that covered it. That link is what distinguishes a request that was granted from one that was quietly narrowed.
Why verification differs between search engines
Each engine runs its own queue and its own assessment, so identical requests can produce different outcomes. Verifying on bing.com is therefore a separate action rather than a formality after checking somewhere else.
openDMCA records dispatch and verification as distinct states on every leak, so a request that was accepted and a URL that is genuinely absent are never collapsed into one number.
openDMCA gives the first two hops away: you can open check a single URL and run it on a URL of your own, with no account and nothing uploaded.
One thing that catches people out on bing.com
Because other search products draw on the bing.com index, verifying there tells you about more than one destination at once — a removal that landed here has usually propagated to them, and one that did not is still returning in places a creator never thought to check. It is the highest-leverage single verification in the set.
Frequently asked questions
The result is gone from one engine but not bing.com.
Separate indexes, separate queues, separate assessments. The second engine needs its own request, and its own verification afterwards.
How long before I re-check?
openDMCA publishes no fixed timeline for any engine. A check after a few days and another later separates slow propagation from a request that was not granted.
Do I need to check the engines that use this index?
Once, to confirm propagation. If a removal landed on bing.com and a downstream product still returns it, that is worth knowing before assuming the job is finished.
Check one URL yourself before you assume it is gone — free, no account.