Hostname
programmap.lavc.edu
Last fetched
programmap.lavc.edu resolves to 100.22.44.22, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. programmap.lavc.edu 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
- 100.22.44.22
100.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.227.198.54
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.238.244.208
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.149.210.217
54.148.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.244.250.160
54.244.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.69.156.69
54.68.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for programmap.lavc.edu is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for programmap.lavc.edu. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-211.awsdns-26.com
- ns-770.awsdns-32.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1052.awsdns-03.org
- ns-1988.awsdns-56.co.uk
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
Threat-feed evidence
History
Related pages
Pivot from programmap.lavc.edu 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: "programmap.lavc.edu"})-[: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.