Skip to content
AdminKit

Is port 47808 (BACnet/IP) exposed to the internet?

AdminKit explains why an exposed port 47808 matters for building operators: it's the UDP port BACnet/IP uses to let HVAC, lighting and access-control systems talk to a central controller, and because BACnet/IP was designed in 1995 with no built-in authentication, anything that can reach port 47808 can typically send it commands.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • UDP 47808 (hex 0xBAC0) is the default BACnet/IP port. Building controllers, supervisory workstations, BACnet routers and broadcast managers all listen on it.
  • Plain BACnet/IP has no login. Anything that can send a packet to 47808 can usually read points and often write them.
  • The standard’s answer is BACnet Secure Connect, added as a separate data link with TLS and certificates. Installed BACnet/IP controllers keep running the old transport until someone migrates them.
  • AdminKit’s port check lists 47808 as “not scanned” because it tests TCP only. Confirm UDP 47808 with a BACnet-aware probe from outside, and find the listener inside.

What is listening on port 47808?

BACnet/IP is the IP-based variant of BACnet, the industry-standard protocol for building automation — HVAC controllers, lighting schedules, fire and life-safety monitoring points, and access-control door controllers from different manufacturers all use it to interoperate on the same network. CISA’s Internet Exposure Reduction Guidance names port 47808 directly among the ports building and industrial operators should not expose to the internet.

The number itself is a small mnemonic: 47808 is 0xBAC0 in hexadecimal. In a typical commercial building, these are the kinds of devices that answer on it:

Device on the BACnet/IP networkTypical roleWhy it matters if reachable from outside
Field and plant controllersRun air handlers, chillers, boilers, pumps, VAV boxesTheir setpoints, schedules and output commands are BACnet points
Lighting and access-control panelsSwitch zones, hold or release door outputsThe same read/write model applies to doors and lights
Supervisory controllers and BMS serversCollect points, run schedules and alarms, serve the operator’s screensThey hold the list of every device on the site
BACnet routers and IP gatewaysConnect serial (MS/TP) controllers to the IP networkOne address gives a path to many controllers behind it
BACnet Broadcast Management Devices (BBMDs)Relay broadcasts between IP subnetsCan let an outside host see the whole site’s broadcasts

A single forwarded port can therefore reach far more than one box. A router or gateway behind the forward passes BACnet requests on to controllers that were never directly connected to the IP network at all.

Why does BACnet/IP have no authentication?

BACnet’s original 1995 design assumed a physically isolated building network where every device on the wire was already trusted — there’s no concept of a username, password or permission check anywhere in the base protocol’s normal read and write services. If port 47808 is reachable from the internet, anything that can send it a UDP packet can typically read and write points on the building network — changing HVAC setpoints, disabling alarms, or manipulating access-control points — with nothing checking who’s asking.

The standard’s committee publishes its changes as addenda to ANSI/ASHRAE Standard 135, and the list of addenda on bacnet.org shows how the security story moved. Two addenda approved on the same day, 18 November 2019, mark the shift. Addendum 135-2016bj introduced “BACnet Secure Connect Datalink Layer Option”. Addendum 135-2016by removed Clause 24, the standard’s older Network Security clause. Later addenda filled in the operating details for BACnet/SC: 135-2020cd added a “TLS V1.3 Cipher Suite Application Profile for BACnet/SC”, and others cover certificate replacement and a file format for certificate authority requirements.

In other words, the standard’s own direction is to protect BACnet traffic by carrying it over a secured data link, rather than adding a login to BACnet/IP. That is a sound design, but it means a BACnet/IP controller stays unauthenticated for its whole life unless it is replaced or moved to BACnet/SC. Controllers in buildings are expected to last a long time, so expect plain BACnet/IP on most sites for years. BACnet’s lack of built-in authentication isn’t unique to building automation: SNMP, used for monitoring routers and switches, has the same problem, relying on a default plaintext “community string” instead of a real credential — see is port 161 (SNMP) exposed.

What can someone do through an exposed port 47808?

Enough to change how the building behaves. A stranger can ask every device to identify itself, read names, locations, vendor and firmware details, and write to points that accept writes. The full list of BACnet services that matter, and how BBMD foreign-device registration widens one exposed address into a view of the whole site, is set out in BACnet/IP exposure in building automation. The short version for this page: an exposed 47808 leaks the site’s equipment list on the first request, and it accepts commands on the second.

How does a building network end up exposed?

It’s almost never a deliberate choice. A building’s BACnet segment gets bridged to the general IT network for remote monitoring or vendor support convenience, and a misconfigured firewall rule or remote-access tool added for one purpose ends up reaching further than intended. Two details make UDP 47808 easy to miss in a review:

  • Router port-forward lists split TCP and UDP. A rule for “47808 UDP” or “Both” sits in the same table as the web and VPN forwards, and a review that only reads TCP entries skips it.
  • Exposure inventories often test TCP. A TCP-only scan, including AdminKit’s, can report a clean result while UDP 47808 is wide open.

How do you read AdminKit’s port check for 47808?

AdminKit’s open ports check tests only the public IP you are browsing from, and it does so with TCP connections. BACnet/IP and CoAP are on its default list so that they appear in the result, but they are reported, not tested. Confirm your current public IP first with what is my IP, then read the result like this:

What the result showsWhat it tells you about BACnet/IP
“Not scanned (UDP, not checked by this tool): 47808 (BACnet/IP), 5683 (CoAP)”Nothing. This line appears on every result; it is a reminder, not a finding
Summary “0/9 TCP port(s) open” with an OK statusOnly the nine TCP ports were tested. UDP 47808 may still be reachable
TCP 80, 443 or 8080 open on a site with a BMSA web front-end for the building system may be exposed; check it, and test UDP 47808 too

How do you confirm port 47808 from outside?

A plain UDP test with nc -u is weak, because UDP has no handshake: a silent port could be open, filtered or closed with the ICMP reply dropped. Use a probe that speaks BACnet. The Nmap bacnet-info script sends standard BACnet requests; its documentation notes that “requests and responses are via UDP 47808”, so the machine you test from must be able to receive replies on that port. From a connection outside the building network, against your own public address only (a documentation address is shown):

sudo nmap -sU -Pn -p 47808 --script bacnet-info 203.0.113.40

Device fields in the output (vendor, model, firmware, object name) mean a BACnet device answers from the internet. The full result table, with what each Nmap state means, is in the BACnet exposure guide. If your site runs BACnet/IP on a second port such as 47809 for a separate network, test that too.

How do you find the listener inside the building?

An outside test shows that something answers; it doesn’t say which device. Work from the router inward:

  1. On the router or firewall, list inbound rules and forwards for UDP 47808 (and any other BACnet ports in use). Note the internal address each one points to.
  2. On that host, confirm what is bound to the port. On a Linux gateway or BMS server:
$ ss -ulnp | grep 47808
UNCONN 0  0  0.0.0.0:47808  0.0.0.0:*  users:(("bms-server",pid=812,fd=9))

On a Windows BMS workstation, Get-NetUDPEndpoint -LocalPort 47808 in PowerShell gives the same answer with the owning process ID. The output above is illustrative; the process name will be whatever your BMS software is called.

  1. If the address is a controller, router or BBMD rather than a server, look it up in the BMS device list and ask the integrator why it has a public path. Embedded controllers rarely have a shell you can inspect.

How do you fix an exposed port 47808?

If 47808 responds from outside: segment the BACnet network behind its own firewall, remove any rule that exposes 47808 directly to the internet, and if remote access is genuinely needed, put it behind a VPN or a purpose-built OT remote-access tunnel rather than a raw forwarded port, consistent with NIST SP 800-82’s network-segmentation guidance for operational technology. Then re-run the outside probe and keep the dated result with your site records. For new equipment, ask whether it supports BACnet/SC and plan the move when controllers are replaced.

Our full guide, BACnet/IP exposure in building automation, walks through the firewall layout and the questions to ask your building automation vendor. If facilities staff and integrators need remote access without an inbound port, OT Remote Access is a Netbase custom engagement that gives outbound-only, recorded sessions; see factories and facilities for the related checks and services.

Which networks may you test?

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

Why does BACnet/IP have no authentication at all?

It was designed in 1995 for physically isolated building networks, where every device on the wire was already trusted by assumption — that assumption doesn't hold once the network has any path to the internet, but the base protocol's lack of authentication hasn't changed.

Has this been fixed in newer BACnet deployments?

Partially — BACnet Secure Connect (BACnet/SC) adds an optional encrypted, certificate-authenticated transport, but it's additive, and most existing BACnet/IP installations still run the original, unauthenticated version.

Why would a building's BACnet network ever reach the internet?

Almost never deliberately — it's usually a BACnet segment bridged to the general IT network for remote monitoring or vendor support, where a misconfigured firewall rule ends up exposing it further than intended.

Is checking my own building's BACnet exposure something I should do myself?

A basic reachability check — is port 47808 answering from outside — is safe to run yourself against your own network. If you find it exposed and aren't sure how your building's automation network is segmented, that's worth bringing in whoever manages your OT network.

Does AdminKit's port check test port 47808?

No. 47808 is on the check's default list, but BACnet/IP runs over UDP and the check makes TCP connections only, so the result lists 47808 (BACnet/IP) under "Not scanned (UDP, not checked by this tool)". An all-clear on the TCP ports says nothing about BACnet; test 47808 separately with a BACnet-aware probe.

Want AdminKit to watch this for you?

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

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.