IPv4 address
148.153.4.196
Last fetched
148.153.4.196 is announced in 148.153.4.0/24 by CDSC-AS1 - CDS Global Cloud Co., Ltd and geolocates to FR. 148.153.4.196 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
- 148.153.4.0/24
- Announcing network
- CDSC-AS1 - CDS Global Cloud Co., Ltd
- RIR-registered prefix
- 148.153.0.0/16
- RPKI
- not-found
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
- logservice.agora.io
- logservice-rtm.agora.io
- logservice-africa.realtimemesh.com
- logservice.rtemesh.com
- logservice-oversea.rtemesh.com
- logservice-africa.rtesvc.com
- logservice-oversea.sdrtnsvc.com
- logservice-europe.sdrtnsvc.com
- logservice-africa.rtemesh.com
- logservice-europe.rtnmesh.com
- logservice.sdrtnsvc.com
- logservice-oversea.rtnsvc.com
- logservice-europe.rtnsvc.com
- logservice-africa.sdrtnsvc.com
- logservice-europe.realtimemesh.com
- logservice-oversea.sdrtnmesh.com
- logservice-europe.sdrtnmesh.com
- logservice-africa.sdrtnmesh.com
- logservice-europe.rtesvc.com
- logservice-default.rtemesh.com
- logservice.rtnmesh.com
- logservice.rtnsvc.com
- logservice-africa.rtnmesh.com
- logservice.rtesvc.com
- logservice-oversea.realtimesvc.com
- logservice-europe.realtimesvc.com
- logservice-africa.realtimesvc.com
- logservice.sdrtnmesh.com
- logservice.realtimemesh.com
- logservice-europe.rtemesh.com
- logservice-oversea.rtnmesh.com
- logservice-oversea.realtimemesh.com
- log-collector-fr3.agoralab.co
Geographic detail
- City
- Paris, FR
- Country
- FR
- Dominant city of the prefix
- Paris, FR
Threat-feed evidence
History
Related pages
Pivot from 148.153.4.196 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: "148.153.4.196"})
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.