Skip to content

Hostname

chipola.edu

Last fetched

chipola.edu resolves to 107.180.91.8, announced in 107.180.88.0/21 by GO-DADDY-COM-LLC - GoDaddy.com, LLC in US. chipola.edu 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 · chipola.eduRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/chipola.edu

Resolution chain

IPv6 resolution

No AAAA record for chipola.edu is recorded in WhisperGraph.

Attribution

godaddy com

ORIGIN_AS

WHOIS identity

Registrant organisation
chipola college

Subdomains

Subdomain
apply.chipola.edu
autodiscover.chipola.edu
ccweb2.chipola.edu
chipola101.chipola.edu
expressyourself.chipola.edu
files.chipola.edu
learningspace.chipola.edu
my.chipola.edu
ns1.chipola.edu
ns2.chipola.edu
vpn.chipola.edu
webmail.chipola.edu

Showing 12 of 15. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.chipola.edu
  • ns2.chipola.edu
  • 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

MX records

  • chipola-edu.mail.protection.outlook.com

SPF policy

  • include: _spf.academicworks.com
  • include: _spf.alchemer.com
  • include: _spf.mlsend.com
  • include: spf.protection.outlook.com
  • ip: 170.249.180.104
  • ip: 204.134.186.101

Threat-feed evidence

History

Related pages

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

Or query Whisper from your own LLM workflow via the Whisper MCP server.