Skip to content
AdminKit

Is port 7547 (TR-069) exposed beyond your ISP's management network?

Port 7547 runs TR-069 (also called CWMP), the protocol many ISPs use to remotely configure and update the router they gave you. It's a legitimate management channel, not inherently a problem — but in November 2016 a Mirai botnet variant used a flaw in how some routers handled a related command over this exact port to knock roughly 900,000 Deutsche Telekom customers offline in a single weekend.

By AdminKit team, Netbase JSC · Updated October 23, 2026

What’s running on 7547, and why

TR-069 (Technical Report 069, the specification that defines CWMP — the CPE WAN Management Protocol) lets an ISP’s Auto-Configuration Server push firmware updates, change settings and diagnose problems on the router or modem they provided, without a technician visit. It’s a normal, widely deployed management tool — the question isn’t whether TR-069 exists, but whether port 7547 is reachable from anywhere beyond your ISP’s own management network.

The 2016 incident, briefly

In November 2016, a Mirai botnet variant scanned the public internet for devices listening on port 7547 and sent a crafted command exploiting a flaw in how certain router models handled a related TR-064 request. Deutsche Telekom’s own routers weren’t vulnerable to the underlying code-injection, but the volume of malicious scan traffic alone crashed roughly 900,000 of them over a single weekend — widely reported at the time and later documented in the USENIX Security 2017 Mirai study. In the aftermath, affected ISPs restricted public access to port 7547 and pushed firmware patches, which is now the standard configuration for a properly managed ISP router.

How to check your own exposure

AdminKit’s planned open ports check is designed to test whether port 7547 on your public IP responds from outside your ISP’s network. If you manage your own hardware rather than relying on an ISP-provided router, this is worth checking directly.

What to do if it’s reachable

On most ISP-provided routers, TR-069 access is configured by the ISP, not something you can toggle from the device’s own admin page — if port 7547 appears reachable from the broader internet rather than just your ISP’s management network, contact your ISP to ask whether access is properly restricted. If you’ve replaced the ISP router with your own hardware, make sure nothing on it is listening on 7547 at all, since you have no legitimate reason to run a CWMP management endpoint without an ISP operating it.

See our full guide, TR-069/CWMP: why ISPs use it and when it’s a risk, for more on how the 2016 incident unfolded and why it’s widely cited as the reason most ISPs now firewall this port.

Defensive use only

Every check this page links to is for assets you own or are explicitly authorized to test. Never scan, probe, or attempt to connect to a network or device you don’t control — AdminKit’s active checks only ever run against the IP making the request or an asset you’ve verified ownership of. See our Disclaimer and Acceptable Use Policy for the full terms.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Does having TR-069 enabled automatically mean I'm at risk?

No — a well-implemented ACS connection restricted to your ISP's own management network is normal and reasonable. The 2016 incident happened because specific router models mishandled a related command insecurely, and the port was reachable more broadly than it should have been.

What actually happened in the 2016 incident?

A Mirai variant scanned for port 7547 and sent a crafted TR-064 command; Deutsche Telekom's specific routers weren't vulnerable to the underlying code-injection itself, but the volume of malicious scan traffic crashed roughly 900,000 of them anyway.

Can I turn TR-069 off myself?

Usually not on an ISP-provided router — it's typically configured by the ISP and isn't an exposed setting on the router's own admin page. If you're concerned, ask your ISP whether access is restricted to their management network.

Did ISPs fix this after 2016?

Yes — affected ISPs restricted public access to port 7547 and pushed firmware patches, and it's now standard practice for ISPs to firewall this port from the general internet.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.