IPv4 address
77.239.124.10
Last fetched
77.239.124.10 is announced in 77.239.124.0/24 by BANATSYNC-SRL - BANATSYNC SRL and geolocates to NL. 77.239.124.10 is listed by 3 threat feeds; reconciled level LOW.
Threat posture
4.28threat score (procedure-native scale)
LOWListed by 3 threat feeds.
- Threat feeds listing this
- 3
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Tue, 01 Sep 2026 01:20:45 GMT
- Last seen on a feed
- Tue, 29 Sep 2026 00:24:52 GMT
Nutrition Label
Attribution
- Announced prefix
- 77.239.124.0/24
- Announcing network
- BANATSYNC-SRL - BANATSYNC SRL
- RIR-registered prefix
- 77.239.96.0/19
- 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
Geographic detail
- City
- Amsterdam, NL
- Country
- NL
- Dominant city of the prefix
- Amsterdam, NL
Threat-feed listings
- duggytuxy-datashield-critical · blacklists
- cins-score · blacklists
- stamparm-ipsum · blacklists
Threat-feed evidence
History
Related pages
Pivot from 77.239.124.10 into the prefix, network and country that carry it.
Queries
This address's full card — routing attribution, reverse DNS and listed feeds.
MATCH (ip:IPV4 {name: $ip})
OPTIONAL MATCH (ip)-[:BELONGS_TO]->(rp:REGISTERED_PREFIX)
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap)
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH ip, rp, ap, a, an, city, ipc
LIMIT 10
WITH ip,
collect(rp.name) AS registeredPrefixes,
collect({prefix: ap.name, asn: a.name, network: an.name, isMoas: ap.isMoas, rpkiStatus: ap.rpkiStatus, isAnycast: ap.isAnycast, dominantCity: ap.dominantCity}) AS announcements,
collect(city.name) AS cities,
collect(ipc.name) AS countries,
collect(a.name) AS announcerNames,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN)
WITH ip, registeredPrefixes, announcements, cities, countries, announcerNames, primaryAsn,
collect(conflict.name) AS conflictAsns
CALL { WITH primaryAsn MATCH (primaryAsn)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS asnPrefixCount }
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN ip.name AS name,
ip.verdictLevel AS verdictLevel,
ip.verdictScore AS verdictScore,
ip.verdictBlocking AS verdictBlocking,
ip.verdictCoverage AS verdictCoverage,
ip.verdictAdvisory AS verdictAdvisory,
ip.threatSources AS threatSources,
ip.threatFirstSeen AS threatFirstSeen,
ip.threatLastSeen AS threatLastSeen,
ip.isTor AS isTor,
ip.isVpn AS isVpn,
ip.isProxy AS isProxy,
ip.isC2 AS isC2,
ip.isPhishing AS isPhishing,
registeredPrefixes, announcements, cities, countries, announcerNames, conflictAsns,
asnPrefixCount, asnPeerCountRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.