Hostname
tungsten-network.com
Last fetched
tungsten-network.com resolves to 104.17.176.227, announced in 104.17.176.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. tungsten-network.com 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
- 104.17.176.227
104.17.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.19.175.164
104.19.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1052
- Registrant organisation
- hefner christian
- Contact emails
- dns.administrator@kofax.com, kinga.otffinowska@tungsten-network.com, thomas.robinson@ob10.com
Subdomains
Showing 12 of 36. View all subdomains →
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
- beth.ns.cloudflare.com
- noel.ns.cloudflare.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
MX records
- eu-smtp-inbound-1.mimecast.com
- eu-smtp-inbound-2.mimecast.com
- tungstennetwork-com02b.mail.protection.outlook.com
SPF policy
- ip: 52.213.12.139/32
- ip: 52.50.94.168/32
- ip: 195.171.121.190/32
- ip: 38.99.18.35/32
- ip: 210.19.216.83/32
- include: _netblocks.mimecast.com
- include: mktomail.com
- include: spf.protection.outlook.com
- include: _spf.salesforce.com
- mx: tungsten-network.com
- ip: 52.50.170.182
Threat-feed evidence
History
Related pages
Pivot from tungsten-network.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: "tungsten-network.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.