HoneyLabs

UDP traffic

Datagrams matching ip:172.235.50.127 sent to HoneyLabs sensors over UDP in the last 7 days. DNS questions and QUIC client fingerprints are decoded on the sensor. Other datagrams are kept as their first bytes and labelled by protocol where it can be recognised.

A UDP source address can be forged, so each address listed here either sent the traffic or was impersonated by whoever did. UDP traffic is kept out of verdicts, feeds, watchlists and alerts.

Your plan searches up to 7d, so 30d was shortened. Plans

2

Datagrams

1

Source addresses

1

Networks

1

Countries

2

Destination ports

Traffic by type

Unrecognised

2 datagrams from 1 source

Datagrams no decoder recognised. Their first bytes are kept.

Latest Unrecognised datagram, to 5353/udp

·.vb·(·0+*_Q'nMc8f·U5·*_ /fhg$l·

payload bytes
00000000  1a 2e 76 62 18 28 02 30  2b 2a 5f 51 27 6e 4d 63  |..vb.(.0+*_Q'nMc|
00000010  38 66 08 55 35 04 2a 5f  20 2f 66 68 67 24 6c a8  |8f.U5.*_ /fhg$l.|
00000020  d2                                                |.|

Amplification checks

Probes for services that answer a small request with a much larger reply, the property reflection attacks rely on.

ServicePortDatagramsSourcesFactor
mDNS5353/udp112 to 10
SSDP1900/udp1130.8

The factor is how many bytes a reachable server can send back for each byte it receives, as published by CISA in alert TA14-017A.

Destination ports

Networks

Countries

Source addresses (unverified)

AddressNetworkCcSendsDatagramsLast seen (UTC)
172.235.50.127AS63949 Akamai Connected CloudUSUnrecognised22026-10-06 16:25

Latest datagrams