Skip to content

Hostname

a.pinggy.io

Last fetched

a.pinggy.io resolves to 141.94.45.153, announced in 141.94.0.0/16 by OVH - OVH SAS in FR. a.pinggy.io is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Command-and-control

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:44:47 GMT
Last seen on a feed
Mon, 21 Sep 2026 23:09:40 GMT

Nutrition Label

WHISPER CANON · a.pinggy.ioRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/a.pinggy.io

Resolution chain

IPv6 resolution

Attribution

akamai

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for a.pinggy.io. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Mail and authentication

Nameservers

  • ns-275.awsdns-34.com
  • ns-740.awsdns-28.net
  • ns-1312.awsdns-36.org
  • ns-1772.awsdns-29.co.uk

Threat-feed evidence

History

Related pages

Pivot from a.pinggy.io into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "a.pinggy.io"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

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