43.252.193.22

Threat posture

Threat feeds listing this

0

Verdict coverage

no-data

Nutrition Label

Attribution

Announced prefix

43.252.193.0/24

Announcing network

BLAZENET-IN-AP - BlazeNet's Network

RIR-registered prefix

43.252.192.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

• sptbi.com
• booking.sptbi.com
• www.sptbi.com
• acses.spit.ac.in
• adcp.spit.ac.in
• airavat.spit.ac.in
• apply.spit.ac.in
• bhimkatta.spit.ac.in
• blockchain.spit.ac.in
• careers.spit.ac.in
• cexit.spit.ac.in
• conference.spit.ac.in
• consultingclub.spit.ac.in
• courses.spit.ac.in
• cse.spit.ac.in
• csi.spit.ac.in
• drc.spit.ac.in
• dspace.spit.ac.in
• ecell.spit.ac.in
• ela.spit.ac.in
• enactus.spit.ac.in
• extc.spit.ac.in
• face.spit.ac.in
• faculty.spit.ac.in
• fets.spit.ac.in
• financeclub.spit.ac.in
• gpu.spit.ac.in
• hackathon.spit.ac.in
• idealab.spit.ac.in
• ieee.spit.ac.in
• ieee-aess.spit.ac.in
• iete.spit.ac.in
• iic.spit.ac.in
• internship.spit.ac.in
• ircell.spit.ac.in
• itsa.spit.ac.in
• library.spit.ac.in
• lor.spit.ac.in
• mca.spit.ac.in
• msp.spit.ac.in
• naac.spit.ac.in
• nisp.spit.ac.in
• oculus.spit.ac.in
• placements.spit.ac.in
• railwayc.spit.ac.in
• rc.spit.ac.in
• research.spit.ac.in
• rnd.spit.ac.in
• rotaract.spit.ac.in
• sdc.spit.ac.in

Geographic detail

Country

IN

Dominant city of the prefix

Ahmedabad, IN

Threat-feed evidence

History

Related pages

Pivot from 43.252.193.22 into the prefix, network and country that carry it.

• Whisper Internet Directory · Home
• TLD · .com
• Live MOAS conflicts
• Prefix · 43.252.193.0/24
• Network · BLAZENET-IN-AP - BlazeNet's Network
• Country · IN
• Hostname · sptbi.com
• Glossary · What is anycast?

Cypher and MCP

Reproduce this address's routing attribution against graph.whisper.security:

MATCH (ip:IPV4 {name: "43.252.193.22"})
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 country

Or query Whisper from your own LLM workflow via the Whisper MCP server.