public company · US
Netflix
NETFLIX INC
Streaming media.
- Primary official domain
- netflix.com
- Reviewed official domains
- 1 (directory review; organization has not verified)
- Directory source
- BreachScout directory · Suggest a correction
Matching domains, 30 days
32
registrable domains containing the brand; source date or last feed observation
First source-reported, 30 days
1
domains first source-reported within 30 days
First observed, 30 days
45
domains first observed by DomainSpoof in feeds
Email policy (primary domain)
DMARC reject
SPF Could not fully evaluate (sender-specific macros) · Mail: Receives mail (5 MX hosts) · 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
- netflix
- Label aliases
- Netflix
- Official domains
- netflix.com (all)
- Generated spellings
- 102 tracked · 77 observed somewhere · 25 not observed (all)
- Can receive mail
- 22 spellings and 9 reported domains publish MX records · mail at Above.com parking (parking placeholder) 7 · hostedmxserver.com 5 · h-email.net (parking placeholder) 3 · 14 more (77 spellings and 32 reported domains of the last 30 days checked; MX shows the domain can receive mail, not who operates it)
Matching domains with source reports or listings
Source claims are shown separately from our company matches. Default scope: brand in hostname. Choose “All associations” to include source-labelled matches on other sites.
| Domain / hostname | Source claim | Company match (DomainSpoof) | Date (mixed basis) | Latest DNS | Sources / records | Finding details |
|---|---|---|---|---|---|---|
| 14 names with the very common brand name 'netflix' (shown on request) | ||||||
9 registrable domains · 14 hostnames · page 1 of 1
A feed listing or DNS answer alone cannot confirm current phishing. Removal from a feed does not confirm resolution.