dazvo.lol
Appeared in the .lol zone on Friday, September 11, 2026; by the end of that day the census found redirects elsewhere. Full domain report
Signals, not verdicts. A domain appears here because heuristics matched its name, its infrastructure or the page it served on its first day. Where a model has looked at it, that is shown as an opinion with a confidence, not as a finding. Nothing on this page says a site is malicious. Read the evidence and decide for yourself.
Own one of these names and think the listing is wrong? Tell us and a person will look.
What matched
Model opinions
dazvo.lol contains no brand string and serves no content of its own; it simply 302s to the real dns.google, whose Google Public DNS resolver page (and its DNS-name lookup form) supplied all the brand/form signals. A neutral offsite redirect to a legitimate Google property is placeholder behaviour, not impersonation, though the random .lol name on Cloudflare NS is worth re-checking if the redirect target changes.
The domain dazvo.lol redirects to dns.google, creating a deceptive entry point. The attacker owns dazvo.lol (a brand-unrelated .lol domain) but uses it to funnel visitors to Google's actual DNS service, likely harvesting the referrer domain or using it as a credential-capture intermediary in a phishing chain. The redirect pattern—obscure domain → legitimate brand site—is a classic phishing infrastructure tactic, even though the final page is genuine; the abuse lies in the domain registration and
A model looked at the screenshot and page text and wrote what it thought. It can be wrong, and it is not a finding.
What the page looked like on Friday, September 11, 2026
Same data as JSON: /api/zone/domain/dazvo.lol. This page is not indexed by search engines and does not link to the site it describes.