IPv4 address
45.129.229.2
Last fetched
45.129.229.2 is announced in 45.129.229.0/24 by SGGS-AS-AP - SG.GS and geolocates to ID. 45.129.229.2 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
- 45.129.229.0/24
- Announcing network
- SGGS-AS-AP - SG.GS
- RIR-registered prefix
- 45.129.228.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
- mangadex.dev
- danke.moe
- 0.danke.moe
- 0.0.danke.moe
- adfs.0.0.danke.moe
- www.adfs.0.0.danke.moe
- admin.0.0.danke.moe
- www.admin.0.0.danke.moe
- citrix.0.0.danke.moe
- www.citrix.0.0.danke.moe
- dev.0.0.danke.moe
- www.dev.0.0.danke.moe
- ftp.0.0.danke.moe
- www.ftp.0.0.danke.moe
- www.git.0.0.danke.moe
- internal.0.0.danke.moe
- www.internal.0.0.danke.moe
- mx.0.0.danke.moe
- www.mx.0.0.danke.moe
- secure.0.0.danke.moe
- www.secure.0.0.danke.moe
- server.0.0.danke.moe
- www.server.0.0.danke.moe
- staging.0.0.danke.moe
- www.staging.0.0.danke.moe
- web.0.0.danke.moe
- www.web.0.0.danke.moe
- www.0.0.danke.moe
- 00.danke.moe
- blog.00.danke.moe
- www.blog.00.danke.moe
- mx.00.danke.moe
- www.mx.00.danke.moe
- public.00.danke.moe
- www.public.00.danke.moe
- remote.00.danke.moe
- www.remote.00.danke.moe
- server.00.danke.moe
- 3chzuzwyghmiu3n.server.00.danke.moe
- www.server.00.danke.moe
- ssh.00.danke.moe
- test.00.danke.moe
- www.00.danke.moe
- alpha.danke.moe
- www.alpha.danke.moe
- app.danke.moe
- www.app.danke.moe
- blog.danke.moe
- www.blog.danke.moe
- co.danke.moe
Geographic detail
- City
- Denpasar, ID
- Country
- ID
- Dominant city of the prefix
- Denpasar, ID
Threat-feed evidence
History
Related pages
Pivot from 45.129.229.2 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: "45.129.229.2"})
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.