Skip to content

Hostname

flyware.net

Last fetched

flyware.net resolves to 188.166.123.177, announced in 188.166.64.0/18 by DIGITALOCEAN-ASN - DigitalOcean, LLC in NL. flyware.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · flyware.netRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/flyware.net

Resolution chain

IPv6 resolution

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
a26pt9my9bb@networksolutionsprivateregistration.com, ns7kj2va5zm@networksolutionsprivateregistration.com, sg8h64kq5hr@networksolutionsprivateregistration.com, wr4zx5683h6@networksolutionsprivateregistration.com

Subdomains

Subdomain
api.flyware.net
dev-api.flyware.net
eloadsheet.flyware.net
jetstar-eloadsheet.flyware.net
mykonos.flyware.net
test-api.flyware.net
test-eloadsheet.flyware.net
www.flyware.net

Showing 8 of 8 subdomains (8 per page).

Mail and authentication

Nameservers

  • ns1.bdm.microsoftonline.com
  • ns2.bdm.microsoftonline.com
  • ns3.bdm.microsoftonline.com
  • ns4.bdm.microsoftonline.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

  • flyware-net.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from flyware.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: "flyware.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.