Skip to content

Hostname

bigwest.org

Last fetched

bigwest.org resolves to 45.223.113.252, announced in 45.223.113.0/24 by INCAPSULA - Incapsula Inc in US. bigwest.org 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 · bigwest.orgRouting diversity1.5/10Peering density9.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/bigwest.org

Resolution chain

IPv6 resolution

No AAAA record for bigwest.org is recorded in WhisperGraph.

Attribution

incapsula

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
big west conference
Contact emails
aq9ht9q38h4@networksolutionsprivateregistration.com, bk7ye2mt3xz@networksolutionsprivateregistration.com, dc8n52tp7px@networksolutionsprivateregistration.com, dn9734j32fx@networksolutionsprivateregistration.com, gn2sn6zg9fb@networksolutionsprivateregistration.com, kr4su3kr2vt@networksolutionsprivateregistration.com, mq6se8gg3ub@networksolutionsprivateregistration.com, ug84685r2c7@networksolutionsprivateregistration.com, xt4hc98z4j6@networksolutionsprivateregistration.com

Subdomains

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.rackspace.com
  • ns2.rackspace.com
  • 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

  • bigwest-org.mx1.arsmtp.com
  • bigwest-org.mx2.arsmtp.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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

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