IPv4 address
152.32.139.36
Last fetched
152.32.139.36 is announced in 152.32.139.0/24 by UCLOUD-HK-AS-AP - UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED and geolocates to KR. 152.32.139.36 is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- no-data
Nutrition Label
Attribution
- Announced prefix
- 152.32.139.0/24
- Announcing network
- UCLOUD-HK-AS-AP - UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED
- RIR-registered prefix
- 152.32.128.0/18
- RPKI
- valid
Anycast detection
This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.
Reverse DNS
- tax-search.cloud-ip.cc
- swat-check.ezgateway.net
- npooo.opik.net
- nugge.cloud-ip.cc
- guidetx.suredoc.net
- tgide.xubi.org
- ninvoice.taxcloud.kro.kr
- ninvoice.parentinvolvement.in
- doc-suggest.mywire.org
- pnosw.loseyourip.com
- thuide.bumbleshrimp.com
- ndoc.ncloud.casacam.net
- ncloud.casacam.net
- php-config.bumbleshrimp.com
- ssl-connect.webredirect.org
- nstk.nid-tax.dynuddns.net
- nid-tax.dynuddns.net
- nidlog.scheculetx.1cooldns.com
- scheculetx.1cooldns.com
- urgtte.naver.ydns.eu
- nid-auth.petfoodkorea.kr
- dns.php-config.bumbleshrimp.com
- ndoc.ssl-connect.webredirect.org
- nidsign.mylogisoft.com
- ndoc.pnosw.loseyourip.com
- ndoc.nauthorize.r-e.kr
- nid.thuide.bumbleshrimp.com
- nusrtx.dns.army
- pdoc-load-77.doc-suggest.mywire.org
- pload.accesscam.org
- dns.ssl-connect.webredirect.org
- ufood.ddnsguru.com
- tlogn.ddnsgeek.com
- nv-token.crabdance.com
- noiduser.dns.army
- toxcloud.dns.army
- ntsdcom.dns.army
- docsupport.v6.navy
Geographic detail
- City
- Seoul, KR
- Country
- KR
- Dominant city of the prefix
- Seoul, KR
Threat-feed evidence
History
Related pages
Pivot from 152.32.139.36 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "152.32.139.36"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.