Detect Aegea
Aegea is a blog engine created by Ilya Birman.
Detection looks at response headers across 1 fingerprint rules among the site's public responses.
01
Websites using Aegea
Loading website list…
02
Signal classes
PluginView evaluates public page signals in these classes when identifying Aegea. Individual fingerprint rule bodies are proprietary and are not published.
- Response headers
03
Example public indicators for Aegea
Illustrative indicators derived from public catalog metadata for Aegea. A live scan may match additional proprietary rules beyond these examples.
- x-powered-by: E2 ?Aegea v?
04
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known Aegea signature (1 rules) at the time of the scan.
- Does not establish
- A sitewide install of Aegea, an active vendor contract, exclusive use, or that Aegea is still in place today.
05
How to check a site for Aegea
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Aegea signals.
- 2. PluginView reads only public responses (response headers) and scores them against the Aegea signature set (1 rules).
- 3. Review the confidence score and text explanation for Aegea on the results page.
06
Commonly implies
07
FAQ: detecting Aegea
- Can PluginView detect Aegea without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Aegea — typically response headers. It does not bypass authentication or paywalls.
- What category is Aegea?
- Aegea is classified under Blogs in the PluginView directory.
- How many fingerprint rules cover Aegea?
- This reference currently tracks 1 fingerprint rule across response headers. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Aegea?
- Illustrative public indicators for Aegea include x-powered-by: E2 ?Aegea v?. A live scan may match additional proprietary rules beyond these examples.