Hostname
s3.com.tw
Last fetched
s3.com.tw resolves to 104.20.29.191, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. s3.com.tw 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
- 104.20.29.191
104.20.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.159.90
172.66.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.239.83.103
18.239.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.83.21
18.239.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.83.30
18.239.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 18.239.83.59
18.239.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.164.53.31
3.164.53.0/24 · AMAZON-02 - Amazon.com, Inc. · Cape Town, ZA
- 3.164.53.37
3.164.53.0/24 · AMAZON-02 - Amazon.com, Inc. · Cape Town, ZA
- 3.164.53.75
3.164.53.0/24 · AMAZON-02 - Amazon.com, Inc. · Cape Town, ZA
- 3.164.53.87
3.164.53.0/24 · AMAZON-02 - Amazon.com, Inc. · Cape Town, ZA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrant organisation
- ?????????? lu kang enterprise co.,
- Contact emails
- savager0215@pchome.com.tw
Subdomains
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
Mail and authentication
Nameservers
- brenda.ns.cloudflare.com
- kurt.ns.cloudflare.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- ip: 61.218.22.0/24
- ip: 61.222.8.0/24
Threat-feed evidence
History
Related pages
Pivot from s3.com.tw 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: "s3.com.tw"})-[: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.