IPv4 address
91.201.52.207
Last fetched
91.201.52.207 is announced in 91.201.52.0/24 by INTERNET-PRO-AS - Internet-Pro LLC and geolocates to RU. 91.201.52.207 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
- 91.201.52.0/24
- Announcing network
- INTERNET-PRO-AS - Internet-Pro LLC
- RIR-registered prefix
- 91.201.52.0/22
- 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
- www.besttravel.am
- asana.by
- www.asana.by
- dverca-kamina.by
- www.dverca-kamina.by
- mehanikenn.by
- www.mehanikenn.by
- rezka-lazernaya.by
- www.rezka-lazernaya.by
- antireider.com
- www.antireider.com
- bankbau.com
- www.bankbau.com
- besserbau.com
- dobedohostel.com
- www.dobedohostel.com
- gordeychuk.com
- imbullconstruction.com
- www.imbullconstruction.com
- jaluzion.com
- konstryktiv.com
- kazan.konstryktiv.com
- www.kazan.konstryktiv.com
- novosibirsk.konstryktiv.com
- www.novosibirsk.konstryktiv.com
- perm.konstryktiv.com
- www.perm.konstryktiv.com
- spb.konstryktiv.com
- www.spb.konstryktiv.com
- www.konstryktiv.com
- kr-dom.com
- cdn2.kr-dom.com
- www.cdn2.kr-dom.com
- cdn3.kr-dom.com
- www.cdn3.kr-dom.com
- www.kr-dom.com
- krsnakatha.com
- www.krsnakatha.com
- miravtoremonta.com
- www.miravtoremonta.com
- prom-energo.com
- www.prom-energo.com
- veselkin.com
- old.veselkin.com
- www.old.veselkin.com
- www.veselkin.com
- xn--b1addlaclwgjdqle8g.com
- www.xn--b1addlaclwgjdqle8g.com
- zaborprof.com
- www.zaborprof.com
Geographic detail
- City
- Yekaterinburg, RU
- Country
- RU
- Dominant city of the prefix
- Yekaterinburg, RU
Threat-feed evidence
History
Related pages
Pivot from 91.201.52.207 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: "91.201.52.207"})
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.