Monitor what browsers and attackers actually see when they connect to a hosted domain — not what the server reports about itself.
AIDE probes the live HTTP and TCP surface of every monitored domain: security headers, TLS posture, dangerous open ports, technology fingerprinting, CVE cross-referencing and infrastructure dependency mapping. Findings are scored and tied to the same domain risk model as DNS, SSL and email.
What teams get on this page
Security header and TLS posture across every endpoint
Dangerous port exposure with per-port severity scoring
CVE-matched software versions with remediation context
What hosting security monitoring answers
Most monitoring tools confirm availability. Hosting security monitoring confirms whether the configuration that responds is safe.
Is the server leaking version information
Server and framework version headers in HTTP responses give attackers direct access to CVE databases without any additional probing.
Which dangerous ports are open to the internet
Database ports like MySQL 3306, Redis 6379 and RDP 3389 exposed to the public internet are routinely targeted in automated scans within hours of exposure.
Is the CMS or plugin stack vulnerable
A WordPress or Drupal installation running a version with a known remote-code-execution CVE is an exploitable target regardless of how good the rest of the configuration is.
What AIDE checks on the web surface
AIDE probes the live application layer, not self-reported configuration, so findings reflect actual exposure.
Security header audit
Check for HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy — each missing header mapped to the attack class it enables.
Port exposure scanning
Probe 21 ports including databases (MySQL, Redis, MongoDB, MSSQL), remote desktop (RDP), and mail relays — with per-port severity reflecting real-world attack frequency.
Technology fingerprinting and CVE matching
Detect 50+ technologies by version and cross-reference against a curated CVE database so a WordPress site with a critical RCE vulnerability gets a concrete penalty and a remediation link.
Infrastructure intelligence
Map the hosting provider, CDN, WAF, ASN, geolocation, shared hosting neighbours and third-party scripts loaded in the page — building a full supply-chain dependency picture.
How this fits into the platform
Hosting security findings become more actionable when they sit alongside DNS, SSL and the domain risk score.
AIDE incorporates hosting security as one of five scoring pillars. A server with MySQL exposed on port 3306 and a missing CSP does not just get a bad hosting score — it caps the domain risk score at High Risk because one critical finding defines the overall posture.
Related feature pages
SSL monitoring
TLS version enforcement and cipher suite audits sit alongside security header and port checks in the full web surface picture.
Subdomain discovery
Hosting security findings are most useful when they cover the full subdomain estate, not just the apex domain.
DNS monitoring
Infrastructure intelligence from hosting security connects to DNS provider changes and nameserver events in a shared domain timeline.
Start monitoring the web surface that attackers actually probe, not the one documented in a control sheet.
AIDE adds hosting security to the same platform as DNS, SSL, email, and uptime so teams get one scored operating model across the full infrastructure stack.