Skip to content

Hostname

125779.com

Last fetched

125779.com resolves to 104.21.5.135, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. 125779.com 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
Tue, 22 Sep 2026 23:26:40 GMT

Nutrition Label

WHISPER CANON · 125779.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint10.0/10canon.whisper.security/host/125779.com

Resolution chain

IPv6 resolution

No AAAA record for 125779.com is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:3862
Registrant organisation
999
Contact emails
3012893818@qq.com, mrp1@qq.com, temp@ename.com

Subdomains

Subdomain
m.125779.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • margot.ns.cloudflare.com
  • theo.ns.cloudflare.com
  • ns1.domainnamedns.com
  • ns2.domainnamedns.com
  • ns3.domainnamedns.com
  • ns4.domainnamedns.com
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net
  • 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 125779.com 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: "125779.com"})-[: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.