Hostname
yes.my
Last fetched
yes.my resolves to 20.43.132.130, announced in 20.40.0.0/13 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in SG. yes.my 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
- 20.43.132.130
20.40.0.0/13 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Singapore, SG
IPv6 resolution
No AAAA record for yes.my is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrant organisation
- ytl communications sdn bhd (793634-v)
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
- ns0.yes.my
- ns1.yes.my
MX records
- yes-my.mail.protection.outlook.com
SPF policy
- include: _spf.google.com
- include: spf.protection.outlook.com
- a: yes.my
- ip: 14.1.197.34
- ip: 183.78.1.135
- ip: 183.78.1.136
- ip: 183.78.1.138
- ip: 183.78.1.139
- ip: 183.78.1.140
- ip: 183.78.1.141
- ip: 183.78.1.148
- ip: 183.78.1.149
- ip: 183.78.4.145
- ip: 183.78.4.240
- ip: 183.78.4.241
- ip: 183.78.4.242
- ip: 183.78.4.243
- ip: 183.78.4.244
- ip: 183.78.4.245
- ip: 183.78.9.2
Threat-feed evidence
History
Related pages
Pivot from yes.my 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: "yes.my"})-[: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.