You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- custom request headers, cookies, and raw HTTP request templates;
62
62
- response filters by status, size, text, regex, and body length;
63
63
- smart auto-calibration for soft-404, wildcard, catch-all, semantic response-diff, and DNS wildcard cases;
64
-
- technology fingerprint detection for CMS, ecommerce platforms, frameworks, and runtime stacks;
64
+
- technology fingerprint detection for CMS, ecommerce platforms, frameworks, runtime stacks, infrastructure, and HSTS posture;
65
65
- passive WAF detection and WAF-safe scan mode;
66
66
- controlled header and path bypass probes for blocked `401` and `403` resources;
67
67
- resumable scan sessions with checkpoint autosave;
@@ -95,7 +95,7 @@ OpenDoor focuses on **context-aware discovery** instead of blind enumeration.
95
95
96
96
## 🧬 Recognized technologies
97
97
98
-
OpenDoor includes a heuristic fingerprint engine for detecting probable application stacks, CMS platforms, frameworks, site builders, static-site tooling, infrastructure providers, and WAF / anti-bot systems.
98
+
OpenDoor includes a heuristic fingerprint engine for detecting probable application stacks, CMS platforms, frameworks, site builders, static-site tooling, infrastructure providers, HSTS / preload readiness, and WAF / anti-bot systems.
99
99
100
100
| Category | Examples |
101
101
|---|---|
@@ -107,6 +107,7 @@ OpenDoor includes a heuristic fingerprint engine for detecting probable applicat
Copy file name to clipboardExpand all lines: docs/Usage.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -450,10 +450,37 @@ Fingerprinting is useful for:
450
450
- identifying static hosting or CDN providers;
451
451
- adjusting filters and scan strategy.
452
452
453
+
After fingerprinting finishes, OpenDoor prints a short pre-scan summary and then continues with the requested scan:
454
+
455
+
```text
456
+
Fingerprint result: cms/WordPress (95%)
457
+
Web stack: WordPress | PHP | Cloudflare
458
+
Security posture: HSTS preload-ready
459
+
```
460
+
461
+
Detailed fingerprint metadata remains available in reports and in the final standard summary.
462
+
453
463
454
464
OpenDoor 5.14.5 expands the passive fingerprint catalog with selected regional CMS, site-builder and strong HTTP-visible infrastructure signatures, including InstantCMS, Duda, Hostinger Website Builder, CMS.S3 / Megagroup, Webasyst / Shop-Script, Discuz!, NetCat, Hostinger, DDoS-Guard and Tencent Cloud.
455
465
456
466
467
+
OpenDoor 5.15.2 also adds offline HSTS / preload-readiness detection to the same `--fingerprint` pass. It checks only the target host response and does not call external preload-status services. Report metadata is stored as `fingerprint.security_headers.hsts`.
Copy file name to clipboardExpand all lines: docs/detection/fingerprinting.md
+61Lines changed: 61 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,22 @@ opendoor \
45
45
46
46
---
47
47
48
+
## Compact pre-scan summary
49
+
50
+
When fingerprinting is enabled, OpenDoor prints a compact summary immediately after the fingerprint pass and before dictionary enumeration starts. This gives operators an early target profile without waiting for report generation.
51
+
52
+
Example:
53
+
54
+
```text
55
+
Fingerprint result: cms/WordPress (95%)
56
+
Web stack: WordPress | PHP | Cloudflare
57
+
Security posture: HSTS preload-ready
58
+
```
59
+
60
+
The compact summary intentionally stays short. Full evidence, candidates, HSTS fields and report-specific metadata remain in JSON, HTML, CSV, SQLite, TXT, STD and SARIF outputs.
61
+
62
+
---
63
+
48
64
## Fingerprinting with reports
49
65
50
66
```shell
@@ -277,6 +293,51 @@ The heuristic fingerprint engine currently recognizes the following platform fam
277
293
278
294
---
279
295
296
+
## Security headers posture
297
+
298
+
When `--fingerprint` is enabled, OpenDoor also performs an offline HSTS posture check against the observed target root response. It does not query external preload services. The check uses only headers returned by the target host.
299
+
300
+
The HSTS result is stored under `fingerprint.security_headers.hsts` in machine-readable reports.
0 commit comments