IPv4 address
80.26.163.48
Last fetched
80.26.163.48 is announced in 80.26.0.0/16 by Telefonica_de_EspaNa - TELEFONICA DE ESPANA S.A.U. and geolocates to ES. 80.26.163.48 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
- 80.26.0.0/16
- Announcing network
- Telefonica_de_EspaNa - TELEFONICA DE ESPANA S.A.U.
- RIR-registered prefix
- 80.24.0.0/13
- 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
- ociotec.com
- adrian.ociotec.com
- ai.ociotec.com
- anchore.ociotec.com
- anthill.ociotec.com
- baserow.ociotec.com
- bookstack.ociotec.com
- budibase.ociotec.com
- chat.ociotec.com
- collabora.ociotec.com
- conway.ociotec.com
- corteza.ociotec.com
- dev.ociotec.com
- docker.ociotec.com
- docmost.ociotec.com
- email.ociotec.com
- gerrit.ociotec.com
- git.ociotec.com
- gitea.ociotec.com
- gitlab.ociotec.com
- gocd.ociotec.com
- gogs.ociotec.com
- grafana.ociotec.com
- guacamole.ociotec.com
- host.ociotec.com
- index.ociotec.com
- jellyfin.ociotec.com
- jenkins.ociotec.com
- keycloak.ociotec.com
- leantime.ociotec.com
- mail.ociotec.com
- matomo.ociotec.com
- maze.ociotec.com
- memos.ociotec.com
- nextcloud.ociotec.com
- nodered.ociotec.com
- owncloud.ociotec.com
- paperwork.ociotec.com
- password.ociotec.com
- penpot.ociotec.com
- phpmyadmin.ociotec.com
- pihole.ociotec.com
- piwik.ociotec.com
- planka.ociotec.com
- plantuml.ociotec.com
- poinz.ociotec.com
- portainer.ociotec.com
- prometheus.ociotec.com
- proxy.ociotec.com
- redmine.ociotec.com
Geographic detail
- City
- Chamartin, ES
- Country
- ES
Threat-feed evidence
History
Related pages
Pivot from 80.26.163.48 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: "80.26.163.48"})
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.