Skip to content

Hostname

jstor.com

Last fetched

jstor.com resolves to 151.101.0.152, announced in 151.101.0.0/22 by FASTLY - Fastly, Inc. in CA. jstor.com 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 · jstor.comRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/jstor.com

Resolution chain

IPv6 resolution

No AAAA record for jstor.com is recorded in WhisperGraph.

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
bb8e39ng4hj@networksolutionsprivateregistration.com, cj5pb9js33z@networksolutionsprivateregistration.com, gw6d874m8fb@networksolutionsprivateregistration.com, p72q523s8sv@networksolutionsprivateregistration.com, td5ke3a693f@networksolutionsprivateregistration.com, w498z4r84uy@networksolutionsprivateregistration.com, wa2ah8964fn@networksolutionsprivateregistration.com, wb3fn68u53p@networksolutionsprivateregistration.com

Subdomains

Subdomain
www.jstor.com

Showing 1 of 1 subdomain (1 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

  • usaeaz1ns03.ithaka.org
  • usaeaz1ns05.ithaka.org
  • usmiaa1ns03.ithaka.org
  • usnjpr2ns01.ithaka.org
  • usnjpr2ns02.ithaka.org
  • usnjpr2ns04.ithaka.org
  • usnyny1ns05.ithaka.org

Threat-feed evidence

History

Related pages

Pivot from jstor.com 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: "jstor.com"})-[: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.