IPv4 address
116.202.65.212
Last fetched
116.202.65.212 is announced in 116.202.0.0/16 by HETZNER-AS - Hetzner Online GmbH and geolocates to DE. 116.202.65.212 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
- 116.202.0.0/16
- Announcing network
- HETZNER-AS - Hetzner Online GmbH
- RIR-registered prefix
- 116.202.0.0/15
- 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
- cabbage.be
- 00163e2e5ca4.cabbage.be
- abogadojuanpautodasesoriacabezaalbarcpreview.cabbage.be
- admin.cabbage.be
- airflow-stag.cabbage.be
- alpha-superset.cabbage.be
- api.cabbage.be
- app.cabbage.be
- autoconfig.cabbage.be
- autodiscover.cabbage.be
- bbs.cabbage.be
- beta.cabbage.be
- bibli.cabbage.be
- blog.cabbage.be
- demo.cabbage.be
- dev.cabbage.be
- e8bd19a6-5a3d-11ec-a4c6-00163e2e5ca4.cabbage.be
- forum.cabbage.be
- git.cabbage.be
- jenkins-production.cabbage.be
- jenkins-std.cabbage.be
- leafs.cabbage.be
- m.cabbage.be
- magento.cabbage.be
- old.cabbage.be
- preview.cabbage.be
- prod.cabbage.be
- production.cabbage.be
- secure.cabbage.be
- shop.cabbage.be
- stag-airflow.cabbage.be
- staging.cabbage.be
- std.cabbage.be
- std-superset.cabbage.be
- store.cabbage.be
- superset-prod.cabbage.be
- superset-test.cabbage.be
- swimmer.cabbage.be
- test.cabbage.be
- web.cabbage.be
- www.cabbage.be
- wwwleafs.cabbage.be
- wwwold.cabbage.be
- wwwsecure.cabbage.be
- wwwstag-airflow.cabbage.be
- wwwstaging.cabbage.be
- wwwstd.cabbage.be
- wwwwwwold.cabbage.be
- wwwwwwswimmer.cabbage.be
- wwwwwwwwwswimmer.cabbage.be
Geographic detail
- City
- Nuremberg, DE
- Country
- DE
Threat-feed evidence
History
Related pages
Pivot from 116.202.65.212 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: "116.202.65.212"})
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.