IPv4 address
82.223.216.136
Last fetched
82.223.216.136 is announced in 82.223.0.0/16 by IONOS-AS - IONOS SE and geolocates to ES. 82.223.216.136 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
- 82.223.0.0/16
- Announcing network
- IONOS-AS - IONOS SE
- RIR-registered prefix
- 82.223.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
- padelnuestro.ar
- www.padelnuestro.ar
- padelnuestro.at
- www.padelnuestro.at
- padelnuestro.be
- www.padelnuestro.be
- padelnuestro.bh
- www.padelnuestro.bh
- padelnuestro.ch
- www.padelnuestro.ch
- clubpremierpadel.com
- padelmania.com
- blog.padelmania.com
- dev.padelmania.com
- staging.padelmania.com
- staging2.padelmania.com
- www.padelmania.com
- apis.padelnuestro.com
- blog.padelnuestro.com
- www.blog.padelnuestro.com
- bot.padelnuestro.com
- cdndata.padelnuestro.com
- cdnimg.padelnuestro.com
- www.cdnimg.padelnuestro.com
- certificados.padelnuestro.com
- ia.padelnuestro.com
- www.ia.padelnuestro.com
- legacy.padelnuestro.com
- www.legacy.padelnuestro.com
- mekalux.padelnuestro.com
- mm2pro.padelnuestro.com
- www.mm2pro.padelnuestro.com
- monitores.padelnuestro.com
- www.monitores.padelnuestro.com
- n8n.padelnuestro.com
- www.n8n.padelnuestro.com
- plesk.padelnuestro.com
- qr.padelnuestro.com
- www.qr.padelnuestro.com
- robinson.padelnuestro.com
- soporte.padelnuestro.com
- www.soporte.padelnuestro.com
- palasdepadelakkeron.com
- worldpadeltourblog.com
- padelnuestro.de
- www.padelnuestro.de
- padelnuestro.dk
- www.padelnuestro.dk
- padelnuestro.do
- www.padelnuestro.do
Geographic detail
- City
- Madrid, ES
- Country
- ES
Threat-feed evidence
History
Related pages
Pivot from 82.223.216.136 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: "82.223.216.136"})
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.