• We've moved. Our community is now at ownd.sh — latest discussions and updates live there.

[OSINT] REVEAL WEBSITE TECH STACKS, LIVE HOSTS & SERVER DETAILS [2026]

Kinder

Divine
Divine
Kinder Rep
0
0
0
Rep
1714
Kinder Vouches
41
0
0
Vouches
41
Posts
6,022
Likes
8,716
4 YEARS
4 YEARS OF SERVICE
Hidden Content

Ever wondered what's actually running behind a website?

A website can reveal information about its infrastructure through HTTP responses, server headers, redirects, certificates, and publicly detectable technologies.

There's a free, open-source reconnaissance tool called httpx, developed by ProjectDiscovery, that helps you collect this information automatically.

It's commonly used by security researchers, bug bounty hunters, and penetration testers to investigate authorised targets.

WHAT CAN IT DISCOVER?
- Which hosts respond to HTTP or HTTPS

- HTTP status codes

- Website page titles

- Web server information

- Detectable website technologies

- Response times

- Redirect destinations

- TLS certificate information

- Content types and response sizes

- CDN and hosting indicators

- Screenshots of accessible webpages

- HTTP response headers

LINKSOfficial GitHub:

https://github.com/projectdiscovery/httpx

Latest Releases:

https://github.com/projectdiscovery/httpx/releases

Documentation:

https://docs.projectdiscovery.io/tools/httpx/overview

Installation:

https://docs.projectdiscovery.io/tools/httpx/install

Usage Guide:

https://docs.projectdiscovery.io/tools/httpx/usage

STEP 1 — INSTALL HTTPXYou can use a precompiled release, Docker, or Go.

For this guide, we'll use Go.

Download Go:

https://go.dev/dl/

The current httpx repository specifies Go 1.25 or newer as its minimum requirement. Use a current supported Go release.

Verify:

 

Code:

Code:
go version

Then install httpx:

 

Code:

Code:
go install -v github.com/projectdiscovery/httpx/cmd/httpx@latest

Make sure Go's binary directory is available in your PATH.

The ProjectDiscovery tool is different from the Python HTTPX library.

STEP 2 — CHECK A WEBSITEFor the examples below, use a website you own or have permission to assess.

Run:

 

Code:

Code:
httpx -u https://example.com -sc -title

This displays information including:
- The target URL

- HTTP status code

- Page title

A hypothetical result:

 

Code:

Code:
https://example.com [200] [Example Domain]

A

Code:

Code:
200

status usually means the server successfully handled the request.STEP 3 — DETECT WEBSITE TECHNOLOGIESWant to identify the technologies a website appears to use?

Run:

 

Code:

Code:
httpx -u https://example.com -td

The

Code:

Code:
-td

flag enables technology detection.Depending on the website, httpx may identify technologies such as:
- Nginx

- Apache

- WordPress

- React

- Next.js

- Cloudflare

- Bootstrap

- Other detectable frameworks or services

Results depend on publicly visible fingerprints.

Not every framework can be identified accurately.

STEP 4 — IDENTIFY SERVER INFORMATIONRun:

 

Code:

Code:
httpx -u https://example.com -sc -server -rt

This displays:
- HTTP status

- Server header information

- Response time

For example:

 

Code:

Code:
https://example.com [200] [nginx] [145ms]

This is an illustrative result.

A server may hide, modify, or omit its identifying headers.

STEP 5 — CHECK MULTIPLE HOSTSSuppose you're auditing several services belonging to your own business.

Create a file called:

 

Code:

Code:
hosts.txt

Add:

 

Code:

Code:
example.com www.example.com api.example.com status.example.com

Now run:

 

Code:

Code:
httpx -l hosts.txt -sc -title -td

httpx will probe the listed targets and print the results.

This is useful for checking which of your known web services respond.

Only include hosts you control or are authorised to test.

STEP 6 — EXPORT RESULTS TO JSONWant a machine-readable report?

Run:

 

Code:

Code:
httpx -l hosts.txt -sc -title -td -json -o results.jsonl

The output is JSON Lines, with individual JSON objects representing results.

You can process the file using scripts or compatible data-analysis tools.

Useful for documenting a website's public-facing infrastructure.

BONUS — CHECK REDIRECTSWebsites often redirect visitors.

For example:

 

Code:

Code:
http://example.com | v https://example.com

To inspect redirect chains:

 

Code:

Code:
httpx -u http://example.com -fr -include-chain

This follows redirects and includes redirect-chain information.

Useful for troubleshooting unexpected redirects or outdated URLs.

BONUS #2 — CHECK TLS INFORMATIONYou can inspect TLS certificate information for an authorised target.

Run:

 

Code:

Code:
httpx -u https://example.com -tls-grab

Certificate information can help identify:
- Certificate issuers

- Certificate validity

- Subject information

- Related certificate properties

TLS information alone does not establish whether a website is secure.

BONUS #3 — TAKE WEBSITE SCREENSHOTShttpx supports capturing website screenshots.

For example:

 

Code:

Code:
httpx -u https://example.com -screenshot

This requires a supported headless browser environment.

Screenshots can help you visually review web services without manually opening each address.

Useful when comparing multiple applications or checking your organisation's published pages.

BONUS #4 — CHECK RESPONSE HEADERSHTTP headers can reveal useful technical information.

Run:

 

Code:

Code:
httpx -u https://example.com -irh

This includes raw HTTP response header information.

You might find headers relating to:
- Content type

- Caching

- Server configuration

- Security policies

- Reverse proxies

Be careful when interpreting these results.

A missing or unusual header isn't automatically a security vulnerability.

WHY IS THIS USEFUL?Imagine an organisation has several web applications.

 

Code:

Code:
COMPANY INFRASTRUCTURE | +-- MAIN WEBSITE | +-- CUSTOMER PORTAL | +-- PUBLIC API | +-- STATUS PAGE | +-- DOCUMENTATION

Instead of manually checking each one, an authorised security team can collect a consistent overview.

This can help identify:
- Unexpectedly accessible services

- Inconsistent technology configurations

- Old public-facing applications

- Redirect problems

- Certificate issues requiring investigation

Detection results are starting points for investigation, not proof of vulnerabilities.

IMPORTANThttpx actively sends HTTP requests.

Unlike a purely passive OSINT search, those requests reach the target servers.

Only scan assets you own or have authorisation to assess.

Avoid excessive request rates, respect service limits, and don't attempt to bypass access controls.

Also remember:
- A detected technology isn't automatically vulnerable.

- A live hostname isn't necessarily an exposed weakness.

- Technology fingerprints can be incorrect.

- CDN services can conceal origin infrastructure.

- Server headers may not reflect the actual backend software.

IS IT STILL MAINTAINED?Yes.

ProjectDiscovery's official repository is actively maintained and documents the installation procedure, HTTP probing, technology detection, JSON output, TLS information, and screenshots.

The project is distributed under the MIT licence.

SOURCEShttps://github.com/projectdiscovery/httpx

https://docs.projectdiscovery.io/tools/httpx/overview

https://docs.projectdiscovery.io/tools/httpx/install

https://docs.projectdiscovery.io/tools/httpx/usage

If you're interested in website reconnaissance, infrastructure discovery, or cybersecurity research, httpx is a useful addition to your toolkit.

It helps turn a collection of authorised website targets into a structured overview of their publicly visible technical characteristics.

 

WANT MORE HIGH QUALITY SHIT FOR FREE?

CLICK HERE > (MY PROFILE)

Haven't made a account yet? register here (REF LINK)




 

179,172

126,023

1,405,739

Top