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
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.
Certificate domains matching this brand
Names identified in certificate logs that match this company or brand. A brand match does not indicate bad intent or malicious activity.
| Matching domain / name | Matched brand / domain | Match type | First CT observation | Latest CT observation | Distinct certificates | Relationship | Source-reported abuse | Details |
|---|---|---|---|---|---|---|---|---|
sslcert-whatsapp.com1 name · includes wildcard names | Brand token in name | 2026-10-19 05:12 UTC | 2026-10-19 05:16 UTC | 4 | Not assessed | No report in sample coverage | ||
sslcert-whatsapp.com | Brand token in name | 2026-10-19 05:16 UTC | 2026-10-19 05:16 UTC | 2 | Issuer YR1 | |||
*.sslcert-whatsapp.comWildcard certificate name: a pattern, not an observed live host | Brand token in name | 2026-10-19 05:12 UTC | 2026-10-19 05:12 UTC | 2 | Issuer YE1 |
Collected from public certificate-transparency logs since 2026-10-18; 21,530,509 log entries checked so far. 80 logs are read continuously by our CT resolver from the point it started following them; earlier entries are not covered. Names on an organization's official domains are recorded by the resolver for at most 100 names per registrable domain per day, so official-domain name and certificate counts are lower bounds. Times are CT log timestamps, which differ from certificate validity dates. Certificate counts include precertificates and final certificates as separate artifacts. The "Source-reported abuse" badge appears only when an independent source reported that exact name for this organization; a certificate name match never creates it, and "No report in sample coverage" is not a safety verdict. How CT works