Hostname
pij.org
Last fetched
pij.org resolves to 100.50.175.4, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. pij.org 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.50.175.4
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.206.32.119
18.204.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.207.80.35
18.204.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.213.19.18
18.208.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.226.172.132
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.196.55.68
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.216.105.201
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.73.61.216
52.72.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for pij.org is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- palestine-israel journal
- Contact emails
- a428h7gh4rg@networksolutionsprivateregistration.com, hf97v8zj6ud@networksolutionsprivateregistration.com, j83cg9ax8bt@networksolutionsprivateregistration.com, px2dh4798ks@networksolutionsprivateregistration.com, zh4cm2h37ga@networksolutionsprivateregistration.com
Subdomains
| Subdomain |
|---|
| dev.pij.org |
| www.pij.org |
Showing 2 of 2 subdomains (2 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.
Mail and authentication
Nameservers
- ns-87.awsdns-10.com
- ns-854.awsdns-42.net
- ns-1254.awsdns-28.org
- ns-1640.awsdns-13.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 pij.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: "pij.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.