Credential phishing
Fake sign-in pages for email, banking, cloud storage, delivery and payment services, built to collect passwords and codes.
BlockIf you block only one list, block this one. A malware and phishing domain list stops users and devices from reaching credential traps, malware downloads and scam sites, whatever app or link brought them there.
Below: what the list covers, how fast it changes, the formats it ships in, how to deploy it and how to deal with the false positives every security list produces.
In our taxonomy these domains sit in the Malware / Phishing / Suspicious category. The category groups several kinds of risk, so you can treat them as one list or split them by how sure you need to be.
Fake sign-in pages for email, banking, cloud storage, delivery and payment services, built to collect passwords and codes.
BlockDomains serving malicious downloads, fake software updates, booby-trapped documents and drive-by pages.
BlockShops that take payment and never ship, fake investment platforms and prize or survey scams.
BlockLookalike names that copy a known brand with swapped letters, extra words or a different extension.
Block or warnPages that fake a virus alert and push a phone number or a remote access download.
BlockDomains with strong signs of abuse but no confirmed payload yet, such as freshly registered lookalikes.
Warn or blockFor the security team's view of the same data as a feed, with fields and delivery details, read the phishing and malware domain feed guide. Category pages: phishing domains and malicious domains.
Phishing domains are built to look right at a glance. These are the patterns that show up again and again, shown with placeholder names under the reserved .test suffix.
Pattern rules alone overblock, because real companies also register names with words like secure or support. Our category is assigned from what the site does, so a pattern raises suspicion but does not decide the label on its own.
This category behaves differently from content categories. It is smaller than Adult or Shopping at any moment, but it turns over much faster.
Domains currently serving phishing, malware or scams. This is the part that must be blocked today.
Domains that went quiet. Many are dropped or parked, but some return in a later campaign.
Fresh entries arrive every day in the deltas, often clustered around one campaign.
Even a phishing domain can appear among visited domains for a few days while a campaign runs.
Because the live set moves daily, we give exact counts to licence holders rather than print a figure that would age within the week. Full category exports fit easily on resolvers and most firewalls.
Phishing campaigns often run for hours or days, not months. A list that updates weekly is mostly protecting you against last week's attacks.
About 300,000 newly registered domains are categorized every day.
New and changed entries ship as daily files your systems fetch automatically.
New domains are checked again, since many arm their pages after launch.
A second recheck catches domains that went bad, or went quiet, later on.
All other domains are refreshed and accuracy is measured by manual validation.
Pair this list with blocking newly registered domains. Young domains carry a high share of phishing risk, and a short hold on them closes the gap before any label exists.
Not every entry deserves the same action on every network. This table is a sensible default that most security teams adjust over time.
| Entry type | School or kids' device | Office staff | Servers and IoT | ISP default | Notes |
|---|---|---|---|---|---|
| Confirmed phishing | Block | Block | Block | Block | No reason to let anyone through |
| Malware delivery | Block | Block | Block and alert | Block | A hit from a server suggests a compromise |
| Scam storefront | Block | Block | Block | Block or warn | Some ISPs warn to avoid disputes |
| Brand lookalike | Block | Warn | Block | Warn | Warn pages let real businesses through |
| Suspicious, no payload | Block | Warn | Block | Log | Review hits weekly |
Treat a server hit as an incident. Servers and IoT devices rarely have a reason to open phishing or malware domains. A lookup from one usually means something on that machine is already wrong.
Licensed customers receive CSV, Parquet and JSON source files, plus enforcement exports on request. The blocklist formats guide shows every layout in full.
Sinkhole addresses in the examples are documentation addresses. Use an internal server that serves a warning page and logs the client.
Deployment is mostly about coverage and visibility: every device should use the list, and every block should leave a trace you can act on.
Load the list on the resolver every device uses. It protects phones, printers and guests as well as managed laptops.
Block outbound DNS to outside servers and keep browsers from switching to their own encrypted DNS.
Load the same list as an EDL so connections by IP after a cached lookup are still caught.
Laptops off the network need a device agent or a cloud resolver that uses the same data.
Every block is a signal. Forward resolver and firewall logs and alert on repeat hits from one device.
Fetch the daily delta, check it is not empty, and alert if the job fails twice in a row.
Integrating into a security product? See threat intelligence integration and DNS filtering integration.
A wrongly blocked domain on a security list hurts more than on a content list, because users learn to ignore warnings. These are the cases to plan for.
Rechecks after a week and a month also clear domains that have been cleaned up, so entries do not stay blocked forever once a site is safe again.
A block is the start of the story, not the end. When the list stops a lookup, a short routine turns that event into a fixed problem.
Match the resolver or firewall log entry to a device and, where possible, a user.
Check mail, chat and browser history for the link or file that triggered the lookup.
Search logs for other devices that looked up the same domain or its siblings.
If a password was typed into a lure, reset it and review sign-in history.
Purge the message, block the sender and tell users what the lure looked like.
Many campaigns use several domains at once. When one shows up in your logs, look at what else the same device queried in the minutes around it.
Almost every network operator uses this category, but each type of buyer cares about a different detail.
One baseline for every client tenant, with block reports that show the value of the service each month. See MSP web filtering.
Network-wide protection for subscribers who never installed anything, served from the resolver.
Add category data to gateways, email filters and endpoint agents through an OEM licence.
Stop staff reaching lookalikes of their own brand and of their suppliers. See banking web filtering.
Students click fast and share links widely, so the block often happens before anyone reports the message.
Browsers, family apps and VPN apps ship the list as a built-in safe browsing layer.
These are the concerns we hear most often from teams comparing a category list with what they already run.
Attackers rarely rely on a single domain. These neighbouring lists close the routes that phishing and malware campaigns use most.
Domains that host credential phishing pages, deliver malware, run scam storefronts or show strong signs of abuse, such as lookalike names of well-known brands. In our taxonomy they sit in the Malware / Phishing / Suspicious category.
At least daily. Many phishing domains are used for a short campaign and then dropped, so a list that updates weekly misses most of the risk. Our new-domain deltas ship every day.
No single control is enough. A domain list stops users reaching known and suspicious domains from any device, but it works best alongside email filtering, multi-factor authentication, endpoint protection and user training.
A compromised site is a hard case, because the domain is normally safe. Category data can flag it while it is abusive, and you can choose to warn instead of block for domains with a long clean history.
Block confirmed phishing and malware delivery outright. For domains marked suspicious without confirmed abuse, a warning page with a continue button is a reasonable middle ground on staff networks, while schools and kids' devices usually block.
Yes. The domain lookup tool shows how a domain is categorized, and licensed customers can use the lookup API for checks inside their own systems.
An external dynamic list hosted on your own HTTPS server. The firewall fetches it on a schedule, so daily updates arrive without manual work. Check your model's entry limit and subdomain matching rules first.
Whole shared platforms such as big site builders and file hosts are not blocked as domains, because that would break legitimate use for everyone. Phishing on those platforms needs URL-level controls in a proxy, browser protection or email filter.
Yes, under an OEM licence. Checking link domains against the category data at delivery time and again at click time is a common use, and the CSV, Parquet and JSON files load straight into a lookup table.
The category is part of the full database licence, not a separate product. Starter database tiers start from $999; enterprise and OEM licences are quoted per deployment.
License the categorized database with daily new-domain deltas, rechecks at one week and one month, and exports for resolvers, firewalls and SIEMs.