Skip to content

Hostname

why3s.com

Last fetched

why3s.com resolves to 103.138.106.61, announced in 103.138.106.0/24 by ABOVE-AS-AP - AboveNet Communications Taiwan in TW. why3s.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 · why3s.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/why3s.com

Resolution chain

IPv6 resolution

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

Attribution

abovenet taiwan

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1336
Registrant organisation
chih shin lin
Contact emails
service@why3s.com

Subdomains

Mail and authentication

Nameservers

  • ns1.com.why3s.com
  • ns2.com.why3s.com
  • ns3.com.why3s.com

MX records

  • why3s.com

SPF policy

  • a: why3s.com
  • mx: why3s.com
  • include: relay01.why3s.com
  • ip: 103.138.106.61

Threat-feed evidence

History

Related pages

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