IPv4 address
5.128.82.36
Last fetched
5.128.82.36 is announced in 5.128.0.0/16 by NTK - Novotelecom Ltd and geolocates to RU. 5.128.82.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
- 5.128.0.0/16
- Announcing network
- NTK - Novotelecom Ltd
- RIR-registered prefix
- 5.128.0.0/14
- 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
- test.greenrooms.io
- gorodok.net
- 0.gorodok.net
- 11atoday.gorodok.net
- 988.gorodok.net
- a-b.gorodok.net
- a106.gorodok.net
- ac_slater.gorodok.net
- alexk20.gorodok.net
- andy271.gorodok.net
- avtobusiness.gorodok.net
- beket.gorodok.net
- blacknovember.gorodok.net
- ceramics.gorodok.net
- chany.gorodok.net
- chfreeman.gorodok.net
- cite.gorodok.net
- codingtheory.gorodok.net
- www.codingtheory.gorodok.net
- danger.gorodok.net
- delphi6.gorodok.net
- dim-hj.gorodok.net
- dist.gorodok.net
- distortion.gorodok.net
- dnd-nsu.gorodok.net
- doks.gorodok.net
- www.doks.gorodok.net
- domains.gorodok.net
- down.gorodok.net
- downloads.gorodok.net
- dron.gorodok.net
- dru.gorodok.net
- dwu.gorodok.net
- dzinn.gorodok.net
- e-texts.gorodok.net
- economics.gorodok.net
- ejene3.gorodok.net
- erimma.gorodok.net
- ext06.gorodok.net
- www.ext06.gorodok.net
- faq.gorodok.net
- far-ssa.gorodok.net
- fc-uragan.gorodok.net
- www.fc-uragan.gorodok.net
- findme.gorodok.net
- flameberg.gorodok.net
- fomichev.gorodok.net
- freebsd.gorodok.net
- fregate.gorodok.net
- www.futbolka.gorodok.net
Geographic detail
- City
- Novosibirsk, RU
- Country
- RU
- Dominant city of the prefix
- Novosibirsk, RU
Threat-feed evidence
History
Related pages
Pivot from 5.128.82.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: "5.128.82.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.