IPv4 address
45.10.243.63
Last fetched
45.10.243.63 is announced in 45.10.243.0/24 by DDOS-GUARD - DDOS-GUARD LTD and geolocates to RU. 45.10.243.63 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.10.243.0/24
- Announcing network
- DDOS-GUARD - DDOS-GUARD LTD
- RIR-registered prefix
- 45.10.240.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
- riobet676.com
- jagalink.org
- www.jagalink.org
- fastucone.com
- dev.jagalink.org
- staging.jagalink.org
- admin.jagalink.org
- api.jagalink.org
- portal.jagalink.org
- backend.jagalink.org
- backup.jagalink.org
- www.riobet676.com
- login.jagalink.org
- app.jagalink.org
- testing.jagalink.org
- test.jagalink.org
- apps.jagalink.org
- fr.jagalink.org
- cn.jagalink.org
- members.jagalink.org
- blogs.jagalink.org
- photo.jagalink.org
- ipv4.jagalink.org
- jobs.jagalink.org
- i.jagalink.org
- extranet.jagalink.org
- it.jagalink.org
- cloudflare-resolve-to.jagalink.org
- feeds.jagalink.org
- stat.jagalink.org
- ts.jagalink.org
- irc.jagalink.org
- ldap.jagalink.org
- web2.jagalink.org
- facebook.jagalink.org
- cacti.jagalink.org
- online.jagalink.org
- archive.jagalink.org
- ftp2.jagalink.org
- w.jagalink.org
- gmail.jagalink.org
- games.jagalink.org
- helpdesk.jagalink.org
- service.jagalink.org
- webmail2.jagalink.org
- ws.jagalink.org
- upload.jagalink.org
- monitor.jagalink.org
- rss.jagalink.org
- tv.jagalink.org
Geographic detail
- City
- Rostov-on-Don, RU
- Country
- RU
- Dominant city of the prefix
- Rostov-on-Don, RU
Threat-feed evidence
History
Related pages
Pivot from 45.10.243.63 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.10.243.63"})
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.