- Dec 6, 2023
- 889
This is almost certainly not Google itself scanning you maliciously — but rather one of the following:
The ports you listed and the fact it’s UDP traffic strongly suggest this is STUN (Session Traversal Utilities for NAT) traffic, typically used by:
This type of traffic happens when a site tries to establish a peer-to-peer connection — and Chrome (or another app) contacts a Google STUN server to determine your external IP and open ports. It might look like a scan, but it's just part of WebRTC trying to make NAT traversal work.
Most Likely: STUN / WebRTC Traffic
The ports you listed and the fact it’s UDP traffic strongly suggest this is STUN (Session Traversal Utilities for NAT) traffic, typically used by:
- Google Chrome
- WebRTC (video/audio calling)
- Google Meet, Discord, Zoom, or any web app using peer-to-peer connections
This type of traffic happens when a site tries to establish a peer-to-peer connection — and Chrome (or another app) contacts a Google STUN server to determine your external IP and open ports. It might look like a scan, but it's just part of WebRTC trying to make NAT traversal work.