Skip to content

Hostname

bethlehemhigh.org

Last fetched

bethlehemhigh.org resolves to 104.16.158.133, announced in 104.16.144.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. bethlehemhigh.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 · bethlehemhigh.orgRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/bethlehemhigh.org

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
contact privacy inc. customer 013366121
Contact emails
bethlehemhigh.org@contactprivacy.com

Subdomains

Subdomain
admin.bethlehemhigh.org
em4378.bethlehemhigh.org
em4740.bethlehemhigh.org
www.bethlehemhigh.org

Showing 4 of 4 subdomains (4 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

Sample outbound links

Mail and authentication

Nameservers

  • ns10.dnsmadeeasy.com
  • ns11.dnsmadeeasy.com
  • ns12.dnsmadeeasy.com
  • ns13.dnsmadeeasy.com
  • ns14.dnsmadeeasy.com
  • ns15.dnsmadeeasy.com
  • ns1.edlio.com
  • ns2.edlio.com

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

SPF policy

  • ip: 208.64.181.100/32
  • ip: 70.36.20.116/32
  • ip: 205.237.106.3/32
  • ip: 67.23.61.36/32
  • ip: 67.23.62.36/32
  • include: _spf.google.com
  • include: swiftreach.com
  • include: em4378.bethlehemhigh.org
  • include: em4740.bethlehemhigh.org

Threat-feed evidence

History

Related pages

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