📘 Website Knowledge Base
A domain is the human-readable address of a website. During analysis, the system identifies the domain’s IP address, hosting provider, and infrastructure footprint.
- IP Address: The server location where the website is hosted.
- Hosting Provider: The company responsible for running server infrastructure.
- Domain Status: Active, expired, or restricted state of the domain.
A stable domain typically resolves correctly to a consistent IP and uses reliable hosting infrastructure.
The Website Status indicates whether the web server successfully responds to browser requests. It uses standard HTTP status codes to describe the current condition of the website.
- 200 OK — Website is online and responding normally.
- 301 / 302 — Website redirects visitors to another page or HTTPS.
- 400 Bad Request — Invalid request received.
- 401 Unauthorized — Authentication required.
- 403 Forbidden — Access is denied.
- 404 Not Found — Requested page does not exist.
- 429 Too Many Requests — Rate limit exceeded.
- 500 Internal Server Error — Server encountered an error.
- 502 Bad Gateway — Invalid response from upstream server.
- 503 Service Unavailable — Server is temporarily unavailable.
- 504 Gateway Timeout — Upstream server took too long to respond.
Frequent server errors usually indicate configuration problems, maintenance, overload, or infrastructure failures.
WHOIS data provides registration details about a domain.
- Registrar (domain registration company)
- Creation date (first registration date)
- Expiration date (domain expiry)
- Domain status (active, locked, pending deletion)
- Name servers (DNS providers)
WHOIS data helps verify ownership and domain legitimacy. Older domains often indicate trust, while newly registered domains may require deeper inspection.
DNS translates domain names into IP addresses that computers can understand.
- A Records: Maps a domain to an IPv4 address.
- AAAA Records: Maps a domain to an IPv6 address.
- CNAME Records: Creates an alias pointing one hostname to another.
- MX Records: Defines mail servers.
- Name Servers: Identify the authoritative DNS servers.
- TXT Records: Store verification and email security records.
- Reverse DNS (PTR): Maps an IP address back to a hostname.
DNS Misconfiguration Risks:
- Website downtime
- Email delivery failure
- Security vulnerabilities
- Domain hijacking risks
Email authentication ensures only authorized servers can send emails on behalf of a domain.
- MX Records: Define email delivery servers.
- SPF: Specifies allowed sending servers.
- DKIM: Adds digital signature for integrity.
- DMARC: Controls handling of suspicious emails.
Email Security Risks:
- Email spoofing
- Phishing attacks
- Domain reputation damage
SSL encrypts communication between browser and server.
- Issuer (Certificate Authority)
- Organization (certificate owner)
- Validity period
- SANs (Subject Alternative Names)
Security Benefits:
- Prevents data interception
- Protects login credentials
- Enables HTTPS encryption
SSL Risks:
- Expired certificates
- Misconfigured SSL
- Missing encryption
HTTPS encrypts communication between visitors and the website using SSL/TLS certificates.
- HTTPS Forced: Every HTTP request automatically redirects to HTTPS.
- HTTPS Not Forced: Visitors can still access the insecure HTTP version.
- Unknown: The server did not provide enough information to determine enforcement.
Enforcing HTTPS protects passwords, personal information, cookies, and other sensitive data from interception.
HTTP Strict Transport Security (HSTS) instructs browsers to always use HTTPS after the first successful secure connection.
- Prevents SSL stripping attacks
- Automatically upgrades future requests to HTTPS
- Improves long-term transport security
- Works together with HTTPS enforcement
If HSTS is not enabled, users may remain vulnerable to downgrade attacks when first visiting the website.
Subdomains are extensions of a primary domain.
- blog.example.com
- shop.example.com
Used for separating services, APIs, dashboards, or marketing pages. Unused subdomains may become security risks.
An IP address is the numerical identity of a server.
- Routes internet traffic
- Identifies hosting location
- Connects domain to infrastructure
Shared IPs may reveal hosting relationships or expose infrastructure patterns.
IPv4 vs IPv6
- IPv4 is the traditional internet addressing system.
- IPv6 is the modern addressing standard with a much larger address space.
The hosting provider operates the server infrastructure.
- Cloud hosting (AWS, Google Cloud)
- Shared hosting
- Dedicated servers
Hosting quality directly affects speed, uptime, and security.
A CMS is used to build and manage website content.
- WordPress
- Joomla
- Drupal
CMS Version Risk:
- Outdated software vulnerabilities
- Insecure plugins
- Security misconfigurations
Frameworks are development tools used to build websites and applications.
- React (frontend)
- Laravel (backend)
- Vue.js
They improve development speed and provide structured architecture.
A CDN distributes content across global servers.
- Faster loading times
- Reduced latency
- Improved global performance
- DDoS mitigation support
Without a CDN, websites may load slower internationally.
Server software handles HTTP requests and serves website content.
- Apache
- Nginx
It manages routing, performance, and backend delivery.
PHP is a backend scripting language used by many websites.
- Exposing version numbers reveals vulnerabilities
- Helps attackers target outdated systems
Best practice: hide version information publicly.
DNS Misconfiguration
- Broken DNS records
- Missing A/AAAA records
- Incorrect MX configuration
- Unused or dangling CNAME records
Mixed Content
- HTTPS pages loading HTTP images
- HTTP JavaScript files
- HTTP CSS resources
PHP Version Exposure
- Server reveals installed PHP version
- May help attackers identify known vulnerabilities
Website Availability
- 403 Forbidden
- 404 Not Found
- 500 Internal Server Error
- 502 Bad Gateway
- 503 Service Unavailable
- 504 Gateway Timeout
Technology Stack Detection identifies the software and services that power a website. By analyzing HTTP headers, HTML source code, DNS records, SSL certificates, and other public indicators, the scanner can determine the technologies used to build and deliver the site.
- Content Management System (CMS): Platforms used to create and manage website content, such as WordPress, Joomla, or Drupal.
- Frameworks: Development frameworks like Laravel, React, Vue.js, Angular, or Next.js that help developers build modern web applications.
- Server Software: Web server software such as Apache, Nginx, LiteSpeed, Microsoft IIS, or Google Web Server (GWS) that processes incoming requests.
- Content Delivery Network (CDN): Services like Cloudflare, CloudFront, Fastly, or Akamai that improve website speed, reliability, and protection by serving content from servers around the world.
- Detected Technologies: Additional software or services identified from public fingerprints, HTTP headers, JavaScript libraries, cookies, or response metadata.
- Version Information: Publicly exposed version numbers for web servers, frameworks, CMS platforms, or programming languages. Older versions may contain known security vulnerabilities if they are no longer supported.
Understanding a website's technology stack helps assess its infrastructure, security posture, compatibility, and potential maintenance requirements. While not every technology can be detected, publicly available information often provides valuable insights into how a website is built and operated.
Infrastructure information identifies the network behind the website.
- Hosting Provider
- Internet Service Provider (ISP)
- Autonomous System Number (ASN)
- Network Owner
- Reverse DNS
This information helps identify cloud providers, hosting companies, enterprise networks, and CDN providers serving the website.
Performance depends on infrastructure design and optimization.
CDN Impact:
- Faster global access
- Reduced latency
- Lower server load
Without optimization:
- Slow load times
- High server stress
- Poor global experience