Highscore 55 · flagged Saturday, September 26, 2026

supportfacebook.monster

Appeared in the .monster zone on Saturday, September 26, 2026; by the end of that day the census found no web server. 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

brand in the name
matched: facebook
+30
lure words (login, verify, secure…)
matched: support
+26
TLD with a high abuse rate
matched: monster
+8
Registrar
—
Nameserver provider
Nameservers
ns1.dyna-ns.net, ns2.dyna-ns.net
First-day state
no web server
HTTP status
—
Page title
—
Has a form
no
Brand echoed
facebook

Model opinions

Second opinionlooks like abusetarget: Facebookconfidence 75%· claude-opus-5-5

The name pairs the distinctive brand 'facebook' with the support-lure word 'support' on a cheap .monster TLD Meta would not use, a classic setup for fake account-recovery phishing. No web content is live yet, so this is judged as a brand-squat rather than active phishing.

First passsuspicioustarget: Facebookconfidence 65%· claude-haiku-4-5

The domain combines 'support' (a lure word commonly used in phishing) with 'facebook' in a .monster TLD (high-risk for abuse), and is currently unreachable with no content. This pattern is consistent with infrastructure being staged for phishing, but without an active page showing credential capture or impersonation, the evidence is not yet decisive.

A model looked at the screenshot and page text and wrote what it thought. It can be wrong, and it is not a finding.

Same data as JSON: /api/zone/domain/supportfacebook.monster. This page is not indexed by search engines and does not link to the site it describes.