Port 4035WAP Push over HTTP

Port for WAP Push over-the-air delivery using HTTP.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 993 of 4,982 · top 20%

also known as wap-push-http, WAP Push OTA-HTTP

Technical Details

what runs on :4035

WAP Push OTA-HTTP carries WAP Push delivery traffic using HTTP-style request and response exchanges, commonly with push content submitted in an HTTP POST. The registry assigns both TCP and UDP; HTTP deployments normally use TCP, while UDP registration reflects the broader WAP transport environment. Typical payloads include WAP Push protocol content such as Service Indication (SI) and Service Loading (SL), rather than ordinary web pages. Port 4035 is distinct from other WAP ports such as 9200/9201 for WAP session transport and 2948/2949 for WAP Push MMS.

Security Information

exposure of :4035

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

web services averages 3.2 across 187 ports — this one sits 1.2 below.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Traffic is not encrypted by default when carried over ordinary HTTP, although an operator can protect the connection with TLS or a private network. This port should generally be restricted to trusted mobile-network or gateway peers; internet exposure could permit spoofed or unsolicited push delivery, traffic injection, and denial-of-service attempts. It is obsolete and uncommon outside carrier infrastructure.

the 8 most looked-up other ports in web services — 187 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted