Hostname
myway.com
Last fetched
myway.com resolves to 146.75.118.114, announced in 146.75.116.0/22 by FASTLY - Fastly, Inc. in DE. myway.com is listed by 2 threat feeds; reconciled level MEDIUM.
Threat posture
24threat score (procedure-native scale)
MEDIUMListed by 2 threat feeds. Advisory: popularity-trust-offset.
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:50:40 GMT
- Last seen on a feed
- Mon, 14 Sep 2026 00:15:52 GMT
Nutrition Label
Resolution chain
- 146.75.118.114
146.75.116.0/22 · FASTLY - Fastly, Inc. · Frankfurt am Main, DE
- 146.75.122.114
146.75.120.0/22 · FASTLY - Fastly, Inc. · Frankfurt am Main, DE
- 146.75.38.114
146.75.36.0/22 · FASTLY - Fastly, Inc. · Ashburn, US
- 199.232.138.114
199.232.136.0/22 · FASTLY - Fastly, Inc. · Sydney, AU
- 199.232.170.114
199.232.168.0/22 · FASTLY - Fastly, Inc. · Paris, FR
- 199.232.82.114
199.232.80.0/22 · FASTLY - Fastly, Inc. · Marseille, FR
IPv6 resolution
No AAAA record for myway.com is recorded in WhisperGraph.
Attribution
Fastly
cdn · MAIL_RECEIVER, ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- ask applications,
- Contact emails
- dnsmanager@iacapps.com, dnsmanager@mindspark.com
Subdomains
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
- 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
- dns1.p07.nsone.net
- dns2.p07.nsone.net
- dns3.p07.nsone.net
- dns4.p07.nsone.net
SPF policy
- ip: 208.89.132.0/23
- ip: 74.113.232.0/23
- include: spf.bluetie.com
Threat-feed evidence
History
Related pages
Pivot from myway.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: "myway.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.