Hostname
munki.flywire.tech
Last fetched
munki.flywire.tech resolves to 18.239.18.38, announced in 18.239.16.0/21 by AMAZON-02 - Amazon.com, Inc. in NL. munki.flywire.tech 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
- 18.239.18.38
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.18.5
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.18.77
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.18.91
18.239.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 99.84.118.108
99.84.118.0/23 · AMAZON-02 - Amazon.com, Inc. · Denver, US
- 99.84.118.23
99.84.118.0/23 · AMAZON-02 - Amazon.com, Inc. · Denver, US
- 99.84.118.48
99.84.118.0/23 · AMAZON-02 - Amazon.com, Inc. · Denver, US
- 99.84.118.53
99.84.118.0/23 · AMAZON-02 - Amazon.com, Inc. · Denver, US
IPv6 resolution
No AAAA record for munki.flywire.tech is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for munki.flywire.tech. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-4.awsdns-00.com
- ns-703.awsdns-23.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
- ns-1237.awsdns-26.org
- ns-1899.awsdns-45.co.uk
Threat-feed evidence
History
Related pages
Pivot from munki.flywire.tech 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: "munki.flywire.tech"})-[: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.