Hostname
funfly.net
Last fetched
funfly.net resolves to 188.225.25.7, announced in 188.225.25.0/24 by TimeWeb-AS - JSC "TIMEWEB" in RU. funfly.net 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
- known-clean
Nutrition Label
Resolution chain
- 188.225.25.7
188.225.25.0/24 · TimeWeb-AS - JSC "TIMEWEB" · St Petersburg, RU
IPv6 resolution
No AAAA record for funfly.net is recorded in WhisperGraph.
Attribution
jsc timeweb
ORIGIN_AS
WHOIS identity
- Registrar
- iana:228
- Registrant organisation
- buydomains_com
- Contact emails
- 17930802@qq.com, brokerage@buydomains.com, privacy@iisp.com, domain@nicenic.net, 4344645383c6082f0327c35f5f3d29c342d2d5a7869fb8b27d7538656ef802d7@funfly.net.whoisproxy.org, 4a7f7c4c800912b17a23332e752dc380d028816e65d6dc1faa0350a8c3d4439f@funfly.net.whoisproxy.org, 5e2f82d2968aadf14e59a3ee037bf20bd06326d24cb1146c6c58effed9c6fff1@funfly.net.whoisproxy.org, 5ec013f28779a1a5dbdf9ee26de09ecb90828f9ea6200780609c04b11805f4b6@funfly.net.whoisproxy.org, b4bf2eb9d485838a9a359b2b4ebe0f14d6b2c814c98a3b7c0e205dca718b06ff@funfly.net.whoisproxy.org, c07c5a4fcec8eadb2d9209d37ff27785303fc09c259720ada74aeadc9fc0dd08@funfly.net.whoisproxy.org, c7de779390d26a0b52fa3d3eb0f64d4503ceb1140f7dc8d1e6f4790a28ee7eaa@funfly.net.whoisproxy.org
Subdomains
Mail and authentication
Nameservers
- 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
- ns3.timeweb.org
- ns4.timeweb.org
- ns1.timeweb.ru
- ns2.timeweb.ru
MX records
- mx1.timeweb.ru
- mx2.timeweb.ru
SPF policy
- include: _spf.timeweb.ru
Threat-feed evidence
History
Related pages
Pivot from funfly.net 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: "funfly.net"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.