The algorithm scores this router 23/100 - an F. Mercusys is a wholly-owned TP-Link subsidiary incorporated in Shenzhen. It shares TP-Link's factories, firmware teams, supply chain, and Chinese state legal jurisdiction. The DOJ and FCC investigation covers TP-Link's full corporate family. Buying Mercusys to avoid TP-Link's problems does not work - the problems transferred with the ownership.
- TP-Link subsidiary - not an independent brand. Every TP-Link risk factor applies identically to Mercusys.
- Chinese state jurisdiction - Mercusys is incorporated in Shenzhen, legally subject to PRC intelligence laws
- Federal investigation covers TP-Link's full corporate family - Mercusys is included
- New models blocked from FCC authorization - same regulatory status as TP-Link parent
- Active firmware support exists - shared TP-Link firmware infrastructure
- Sold as a budget brand distinct from TP-Link - it is TP-Link hardware under a different badge
- TP-Link subsidiary - identical ownership risk: Mercusys was incorporated as a TP-Link subsidiary. There is no legal, operational, or supply chain separation. The DOJ investigation covers the entire TP-Link corporate family.
- Shared firmware codebase with TP-Link: Mercusys devices run firmware derived from TP-Link's codebase. TP-Link vulnerabilities often have Mercusys equivalents.
FCC & Ban Risk
25
/100
F
Supply chain · FCC status · CVEs · Patch support
Security Capabilities
19
/100
F
Zero-Trust · VPN · Segmentation · Monitoring
🏭 Manufacturer
Chinese-owned (TP-Link subsidiary)
Mercusys Communications Co., Ltd. - wholly owned TP-Link subsidiary, Shenzhen
Manufactured in: China
🛡️ Patch Support
Active
Whether security vulnerabilities are actively being patched
⚠️ Key Finding
critical
TP-Link subsidiary - identical ownership risk
Router Security Updates
Get notified if new vulnerabilities are discovered for your Mercusys Halo H70X. Free, no spam.
🔒
Security capabilities comparison
We benchmark your router against Rio Router across 8 dimensions so you can see exactly what gaps exist - and what a fully-covered setup looks like.
MERCUSYS
your router
Rio Router™
full standard
Zero-Trust Device Admission
Every new device is blocked by default - admin must approve it once, even if it has the right password
Not available
Available
Network Segmentation (VLANs)
Devices on your network are isolated from each other, so a hacked smart TV can't reach your laptop
Partial
Available
Router-Level VPN for All Devices
All traffic - including smart devices that can't run VPN apps - is encrypted before leaving your home
Not available
Available
Domain Allowlisting
Block everything except approved sites; more effective than trying to blacklist billions of harmful URLs
Not available
Available
Granular Password Control
Separate passwords per network zone - changing one doesn't affect others
Partial
Available
Guest Auto-Expiry
Guest devices are automatically removed when they leave; neighbors can't reconnect without re-approval
Not available
Available
Clean Supply Chain
Manufactured outside Chinese legal jurisdiction - not subject to China's National Intelligence Law
Not available
Available
Active Threat Monitoring
DNS filtering, firewall, activity logs, and ongoing security patch support
Partial
Available
We use Rio Router as the benchmark because it’s the only consumer router built to score 8/8 on this framework - it shows you what a fully-covered setup looks like, not just what’s typical.
See Rio →
See all Mercusys models: Mercusys brand overview →
What you should do
1
Treat this exactly as a TP-Link router
2
Replace with a manufacturer outside Chinese legal jurisdiction
This is a TP-Link product with a different logo.
How this was scored · verified March 2026: This rating combines FCC authorization status, manufacturer legal jurisdiction, CVEs from NIST NVD, active patch support status, and CISA advisory mentions. See full methodology →
Reference Data
Known CVEs - Mercusys brand history
From the NIST National Vulnerability Database. Your specific model may or may not be affected.
OS command injection via traceroute. Unauthenticated remote exploitation.
See all Mercusys CVEs: NIST NVD search →
Sources & evidence
All findings trace to publicly verifiable primary sources - US government databases, official FCC filings, and NIST CVE records. No proprietary or anonymous sources are used.
- Public corporate filings ↗
- FCC Equipment Authorization Database ↗
- FCC Covered List · National Security Designation ↗
Full data source documentation: Scoring Methodology & Citations →