Skip to content

Hostname

wingscareer.com

Last fetched

wingscareer.com resolves to 108.138.36.29, announced in 108.138.32.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. wingscareer.com 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 · wingscareer.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/wingscareer.com

Resolution chain

IPv6 resolution

No AAAA record for wingscareer.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
pt sayap mas utama
Contact emails
2cd7a7a1ff3c41aab9532171cf0fa589.protect@whoisguard.com, suwarto.widjaya@wingscorp.com

Subdomains

Subdomain
mymail112.wingscareer.com
mymail113.wingscareer.com
mymail114.wingscareer.com
www.wingscareer.com

Showing 4 of 4 subdomains (4 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-459.awsdns-57.com
  • ns-532.awsdns-02.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-1363.awsdns-42.org
  • ns-1801.awsdns-33.co.uk

MX records

  • mymail112.wingscareer.com
  • mymail113.wingscareer.com
  • mymail114.wingscareer.com
  • mx.wingscorp.com

Threat-feed evidence

History

Related pages

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

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