Skip to content

Hostname

dumps.cc

Last fetched

dumps.cc resolves to 154.85.49.102, announced in 154.85.48.0/21 by Baidu - Beijing Baidu Netcom Science and Technology Co., Ltd. in SG. dumps.cc is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

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

Nutrition Label

WHISPER CANON · dumps.ccRouting diversity1.5/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/dumps.cc

Resolution chain

IPv6 resolution

No AAAA record for dumps.cc is recorded in WhisperGraph.

Attribution

beijing baidu netcom science

DNS_OPERATOR, ORIGIN_AS

WHOIS identity

Registrar
iana:3765
Registrant organisation
bradly remov
Contact emails
stilon88@mail.ru

Subdomains

Subdomain
autodiscover.dumps.cc
cpanel.dumps.cc
cpcalendars.dumps.cc
cpcontacts.dumps.cc
mail.dumps.cc
root.dumps.cc
webdisk.dumps.cc
webmail.dumps.cc
wildcard.dumps.cc
www.dumps.cc

Showing 10 of 10 subdomains (10 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • dumps.cc
  • ns3.my-ndns.com
  • ns4.my-ndns.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

Threat-feed evidence

History

Related pages

Pivot from dumps.cc 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: "dumps.cc"})-[: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.