Hostname
filecabi.net
Last fetched
filecabi.net resolves to 128.14.74.107, announced in 128.14.74.0/24 by ZEN-ECN - Zenlayer Inc in US. filecabi.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
- 128.14.74.107
128.14.74.0/24 · ZEN-ECN - Zenlayer Inc · Los Angeles, US
- 128.14.74.124
128.14.74.0/24 · ZEN-ECN - Zenlayer Inc · Los Angeles, US
- 170.106.193.60
170.106.192.0/21 · TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue · Santa Clara, US
- 44.208.83.180
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.84.240.235
54.84.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
Attribution
zenlayer
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1556
- Registrant organisation
- domain administrator
- Contact emails
- domain@llnw.com
Subdomains
| Subdomain |
|---|
| www.filecabi.net |
Showing 1 of 1 subdomain (1 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.
Mail and authentication
Nameservers
- ns1.dropcatch.com
- ns2.dropcatch.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
- ns1.myhostadmin.net
- ns2.myhostadmin.net
- ns3.myhostadmin.net
- ns4.myhostadmin.net
- ns5.myhostadmin.net
- ns6.myhostadmin.net
MX records
- mail1.namebrightmail.com
- mail2.namebrightmail.com
Threat-feed evidence
History
Related pages
Pivot from filecabi.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: "filecabi.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.