IPv4 address
193.77.51.76
Last fetched
193.77.51.76 is announced in 193.77.0.0/18 by SIOL-NET - Telekom Slovenije, d.d. and geolocates to SI. 193.77.51.76 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
- 193.77.0.0/18
- Announcing network
- SIOL-NET - Telekom Slovenije, d.d.
- RIR-registered prefix
- 193.77.0.0/16
- 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
- pontonmessenger.ngen.at
- test.pontonmessenger.ngen.at
- app.restavracija-manu.com
- app-api.restavracija-manu.com
- app-dev.justcharge.io
- app-new.justcharge.io
- dev-app.justcharge.io
- flower.justcharge.io
- flower-dev.justcharge.io
- ocpp.justcharge.io
- ocpp-dev.justcharge.io
- ocpp16.justcharge.io
- whitelabel.justcharge.io
- app.tapcharge.io
- bsn-77-51-76.static.siol.net
- scada.elektrarnaruse.encom.si
- mta-sts.encom.si
- access.ngen.si
- acroni.ngen.si
- api.ngen.si
- app.ngen.si
- app-api.ngen.si
- app-utils.ngen.si
- mffr.at.ngen.si
- scada.hranilnik1.austria.ngen.si
- comfortclick.ngen.si
- contentserver.ngen.si
- ebs-ext.ngen.si
- eg.ngen.si
- gt.errortracker.ngen.si
- gitlab.ngen.si
- hranilnik1.ngen.si
- scada.hranilnik1.ngen.si
- hranilnik2.ngen.si
- scada.hranilnik2.ngen.si
- hranilnik3.ngen.si
- scada.hranilnik3.ngen.si
- gw1.ipcomm.ngen.si
- gw2.ipcomm.ngen.si
- iskra.ngen.si
- tesla.iskra.ngen.si
- jira.ngen.si
- lb.ngen.si
- moj.ngen.si
- moj-api.ngen.si
- ms.ngen.si
- notify.ngen.si
- odoo-proxy.ngen.si
- oscp.ngen.si
- elpro.powerbank.ngen.si
Geographic detail
- City
- Ljubljana, SI
- Country
- SI
Threat-feed evidence
History
Related pages
Pivot from 193.77.51.76 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: "193.77.51.76"})
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.