Hostname
medtraining.org
Last fetched
medtraining.org resolves to 13.107.213.53, announced in 13.104.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. medtraining.org 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
- 13.107.213.53
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.213.62
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.246.53
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.246.62
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 150.171.109.100
150.171.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Nairobi, KE
- 150.171.109.101
150.171.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Nairobi, KE
IPv6 resolution
No AAAA record for medtraining.org is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:886
- Registrant organisation
- domain privacy service fbo registrant.
- Contact emails
- aorkand@gmail.com
Subdomains
| Subdomain |
|---|
| arkray.medtraining.org |
| ethiopia.medtraining.org |
| ltac.medtraining.org |
| ltacx.medtraining.org |
| www.medtraining.org |
Showing 5 of 5 subdomains (5 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
Mail and authentication
Nameservers
- ns1-35.azure-dns.com
- ns4-35.azure-dns.info
- ns2-35.azure-dns.net
- ns3-35.azure-dns.org
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: amazonses.com
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from medtraining.org 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: "medtraining.org"})-[: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.