Hostname
elac.edu
Last fetched
elac.edu resolves to 6 IPv4 addresses operated by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA.
Nutrition Label
Resolution chain
elac.edu resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.107.213.40 | 13.104.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | CA |
| 13.107.226.45 | 13.104.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | CA |
| 13.107.246.40 | 13.104.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | CA |
| 13.107.253.45 | 13.104.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | CA |
| 150.171.109.100 | 150.171.0.0/16 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | KE |
| 150.171.109.101 | 150.171.0.0/16 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | KE |
WHOIS identity
- Registrar
- —
- Organization
- east los angeles college
- Contact emails
- —
Subdomains
42 observed subdomains of elac.edu.
Showing 25 of 42. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from elac.edu in the public web crawl.
411 sites link to this hostname.
181 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
15 SPF mechanisms authorising senders for elac.edu.
| Mechanism | Target |
|---|---|
| SPF_A | elac-outgoing.elac.edu |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | spf.blackboardconnect.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | verifymyfafsa.com |
| SPF_IP | 136.179.3.130/32 |
| SPF_IP | 142.250.153.26/32 |
| SPF_IP | 198.188.255.102 |
| SPF_IP | 198.188.255.103 |
| SPF_IP | 204.102.73.119 |
| SPF_IP | 204.102.73.44/32 |
| SPF_IP | 216.17.93.137/32 |
| SPF_IP | 67.94.7.12 |
| SPF_IP | 78.153.247.50 |
| SPF_IP | 78.153.247.6/32 |
Related pages
Pivot deeper into the graph from elac.edu.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "elac.edu"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.