Hostname
66win.com.ph
Last fetched
66win.com.ph resolves to 15.197.196.85, announced in 15.197.192.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. 66win.com.ph 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
- 15.197.196.85
15.197.192.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 166.117.150.92
166.117.144.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 166.117.249.126
166.117.240.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 166.117.50.96
166.117.48.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 166.117.165.93
166.117.160.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 13.248.209.120
13.248.208.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 75.2.46.107
- 166.117.222.112
IPv6 resolution
No AAAA record for 66win.com.ph is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for 66win.com.ph. 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.
Subdomains
| Subdomain |
|---|
| a.66win.com.ph |
| b.66win.com.ph |
| m.66win.com.ph |
| wildcard.66win.com.ph |
| ww1.66win.com.ph |
| ww12.66win.com.ph |
Showing 6 of 6 subdomains (6 per page).
Mail and authentication
Nameservers
- ns-55.awsdns-06.com
- a.share-dns.com
- ns-856.awsdns-43.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
- b.share-dns.net
- ns-1216.awsdns-24.org
- ns-1572.awsdns-04.co.uk
Threat-feed evidence
History
Related pages
Pivot from 66win.com.ph 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: "66win.com.ph"})-[: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.