IPv4 address
81.19.75.0
Last fetched
81.19.75.0 is announced in 81.19.64.0/19 by RAMBLER-TELECOM-AS - Rambler Internet Holding LLC and geolocates to RU. 81.19.75.0 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
- 81.19.64.0/19
- Announcing network
- RAMBLER-TELECOM-AS - Rambler Internet Holding LLC
- RIR-registered prefix
- 81.19.64.0/20
- 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
- pfmlink.com
- admin.pfmlink.com
- api.pfmlink.com
- my.pfmlink.com
- static.pfmlink.com
- prfl.io
- pfm.live
- wildcard.pfm.live
- pfmlink.me
- prfl.me
- alfabank.prfl.me
- apitor.prfl.me
- dash.prfl.me
- frihet.prfl.me
- lavka.prfl.me
- lentaonline.prfl.me
- perekrestok.prfl.me
- tinkoff1000.prfl.me
- wildcard.prfl.me
- ai-scenario-tg-bot.perfluence.net
- api.perfluence.net
- auto-publications-tg-bot.perfluence.net
- bapi.perfluence.net
- content-tg-bots.perfluence.net
- dash.perfluence.net
- export.perfluence.net
- feedback.perfluence.net
- ipgeo.perfluence.net
- mgcom.perfluence.net
- nestapi.perfluence.net
- ord-api.perfluence.net
- pawss-api.perfluence.net
- promo-bot.perfluence.net
- rbapi.perfluence.net
- rkn-api.perfluence.net
- rs3api2.perfluence.net
- s3-proxy.perfluence.net
- s3sc.perfluence.net
- static.perfluence.net
- tgbots.perfluence.net
- tolgee.perfluence.net
- video.perfluence.net
- sharry.pro
- bapi.sharry.pro
- dash.sharry.pro
- export.sharry.pro
- mapi.sharry.pro
- meow.sharry.pro
- mobile-bff.sharry.pro
- static.sharry.pro
Geographic detail
- City
- Moscow, RU
- Country
- RU
- Dominant city of the prefix
- Moscow, RU
Threat-feed evidence
History
Related pages
Pivot from 81.19.75.0 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: "81.19.75.0"})
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.