public company · US

Meta (Facebook)

Meta Platforms, Inc.

Facebook, Instagram and WhatsApp.

Primary official domain
facebook.com
Reviewed official domains
5 (directory review; organization has not verified)
Directory source
BreachScout directory · Suggest a correction
Matching domains, 30 days
152
registrable domains containing the brand; source date or last feed observation
First source-reported, 30 days
0
domains first source-reported within 30 days
First observed, 30 days
174
domains first observed by DomainSpoof in feeds
Email policy (primary domain)
DMARC reject
SPF -all · 1/10 lookups · Mail: Receives mail (1 MX host) · checked 2026-10-19 · published policy

What we watch for

Hostnames in phishing feeds and certificate logs are matched on these brand tokens; feed target labels are matched on the aliases. Generated spellings (typos, lure words, look-alike characters, other top-level domains) are derived from the official domains and tokens and checked against feeds, certificate logs and DNS.

Brand tokens
facebookinstagrammetaplatformswhatsapp
Label aliases
Facebook · Instagram · Meta Platforms · WhatsApp · Meta
Official domains
meta.com · facebook.com · fb.com · instagram.com · whatsapp.com (all)
Generated spellings
400 tracked · 179 observed somewhere · 221 not observed (all)
Can receive mail
3 spellings and 32 reported domains publish MX records · mail at Google 6 · iFastNet 4 · Cloudflare Email Routing (mail forwarding) 2 · 22 more (6 spellings and 152 reported domains of the last 30 days checked; MX shows the domain can receive mail, not who operates it)

Generated spellings we track

Spellings generated from this organization's official domains and brand tokens (typos, keyboard slips, lure words, look-alike characters, other top-level domains). Each one is checked against phishing feeds, certificate logs and DNS. A spelling that exists is not a finding and not a verdict: it may be unrelated, legitimate or registered defensively.

Tracked spellings
400
generated 2026-10-19; bounded dictionary, not every possible spelling
Seen in a phishing feed
1
spellings with at least one approved-source feed host on that domain
Seen in certificate logs
6
spellings with a certificate name on that domain in the logs we collect
Resolves
178
spellings that answered a DNS query; 400 of 400 checked so far
Can receive mail
3
spellings with an MX record, of 6 checked · mail at Google 6 · iFastNet 4 · Cloudflare Email Routing (mail forwarding) 2 · show
Listed mail infrastructure
0
mail-enabled spellings whose MX host address or SPF sending range is on an IP list approved for display · a fact about shared addresses, not about who operates the spelling

Lure word added 1 tracked · 1 observed

SpellingDerived fromIn phishing feedIn certificate logsResolvesMailState
verifymeta[.]com
meta.comNot observed
Logged 2026-10-19 – 2026-10-192 certificates, 2 names
Alive191.101.104.19HostingerHostinger (AS47583) · CY212.1.212.33 · Confirmed phishing host address (DomainSpoof, 14 days)HostingerHostinger (AS47583) · CYlast answered 2026-10-19
MXSPFDMARCmail at Hostinger (web / mail hosting) · sends via spf.flockmail.com, Hostinger, MailChannels · checked 2026-10-19
Observed

Other top-level domain 1 tracked · 1 observed

SpellingDerived fromIn phishing feedIn certificate logsResolvesMailState
fb[.]org
fb.comNot observed
Logged 2026-10-19 – 2026-10-192 certificates, 1 name
Alive23.239.28.132Akamai LinodeAkamai Linode (AS63949) · SGlast answered 2026-10-19
MXSPFDMARCmail at Microsoft 365 (consumer mailbox) · DMARC policy quarantine · sends via _u.fb.org._spf.dmarclj.com, Microsoft 365 · checked 2026-10-19
Observed

Character omitted 1 tracked · 1 observed

SpellingDerived fromIn phishing feedIn certificate logsResolvesMailState
whtsapp[.]com
whatsapp.com
Seen 2026-10-18 – 2026-10-181 host, 1 seen in the last 7 days
Not observed
Alive103.224.182.247 · Confirmed phishing host address (DomainSpoof, 14 days)Trellian (Above.com parking)Trellian (Above.com parking) (AS133618) · AUlb-182-247.above.comlast answered 2026-10-19
MXSPFDMARCmail at Above.com parking (parking placeholder) · checked 2026-10-19
Observed

Last feed and certificate-log check 2026-10-19 05:45 UTC. “Not observed” means none of our checks has seen the spelling; it is not proof the name is unregistered. An observed spelling is not a finding: reported abuse appears only under Reported matches, from independent source evidence. Feed presence counts hosts from approved sources only; certificate presence comes from the public logs described on the Certificates tab; DNS checks cover the apex name and are refreshed on a schedule. Under each address: network (AS) and country come from the public iptoasn.com routing dataset; a reverse-DNS name is what the address's owner published. Neither shows who controls the hostname: shared hosting, CDNs and cloud providers put unrelated names behind one address. Mail (MX, SPF, DMARC) is checked only for spellings observed somewhere; mail records show the domain can send or receive mail; they do not show who operates it. The provider named under the chips is read from the first MX host (a curated list of mailbox, hosting, parking, forwarding and registrar services; otherwise the host itself); “sends via” lists the services the SPF record authorises; the DMARC policy is the published p= tag. A red MX or SPF chip names the IP list an address behind the record is on (the MX host's address, or an SPF ip4 range of the record or of the services it includes), checked at page view against the lists approved for display. Mail providers and sending services are shared, so a listing says nothing about who operates the domain. The last bulk DNS check of every tracked spelling finished 2026-10-19 11:34 UTC (784,714 names).