IPv4 address
5.252.35.162
Last fetched
5.252.35.162 is announced in 5.252.35.0/24 by STORMWALL-AS - StormWall s.r.o. and geolocates to DE. 5.252.35.162 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
- 5.252.35.0/24
- Announcing network
- STORMWALL-AS - StormWall s.r.o.
- RIR-registered prefix
- 5.252.32.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
- ns1.absorbemail.com
- ns1.acccmail.com
- ns1.accountae.com
- ns2.accountae.com
- ns1.acdcdcmail.com
- ns1.acromonomail.com
- ns1.acroparemail.com
- ns1.adamanmail.com
- ns1.adenocmail.com
- ns1.adrenocortmail.com
- ns1.affairmail.com
- ns2.affairmail.com
- ns1.airmaiil.com
- ns1.albigmail.com
- ns1.amwomail.com
- ns1.angiocardmail.com
- ns1.antagonix.com
- ns2.antagonix.com
- ns1.anthropomomail.com
- ns1.antismail.com
- ns1.aphromail.com
- ns1.aplotmail.com
- ns1.arachmail.com
- ns1.ationsmail.com
- ns1.atoptomail.com
- ns1.autosuggmail.com
- ns1.bananmail.com
- ns2.bananmail.com
- ns1.baranmail.com
- ns1.bayomail.com
- ns1.berbekmail.com
- ns1.bfirstmail.com
- ns1.biblimail.com
- ns1.bigemaiil.com
- ns1.black1mail.com
- ns1.bormasmail.com
- ns1.botryomail.com
- ns1.bouterk.com
- ns2.bouterk.com
- ns1.boykmail.com
- ns1.br41nmail.com
- ns1.breackmail.com
- ns1.brkngbdmail.com
- ns1.buffsmail.com
- bulltraffic.com
- crm.bulltraffic.com
- mail.bulltraffic.com
- www.bulltraffic.com
- ns1.carcinmail.com
- ns1.catdogmail.com
Geographic detail
- City
- Frankfurt am Main, DE
- Country
- DE
- Dominant city of the prefix
- Frankfurt am Main, DE
Threat-feed evidence
History
Related pages
Pivot from 5.252.35.162 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: "5.252.35.162"})
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.