Check-Host.cc

Domain

docs.example.staging.plesk.tech

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of docs.example.staging.plesk.tech

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
A/AAAA targets
Subdomains
CT + scan + body
Record Types
seen in DNS
Observed Certs
in our scans

DNS Records

A
3.173.161.11, 3.173.161.3, 3.173.161.6, 3.173.161.79, 52.222.214.102, 52.222.214.125, 52.222.214.20, 52.222.214.83
AAAA
MX
NS
TXT
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

04a3c32507909725… cloudflare · nimbus2026
Subject: docs.example.staging.plesk.tech
Issuer: Amazon RSA 2048 M02
SANs: docs.example.staging.plesk.tech
Valid: 2025-06-29 00:00:00 → 2026-07-28 23:59:59
83b64107a498a2aa… cloudflare · nimbus2026
Subject: docs.example.staging.plesk.tech
Issuer: Amazon RSA 2048 M02
SANs: docs.example.staging.plesk.tech
Valid: 2025-06-29 00:00:00 → 2026-07-28 23:59:59
04a3c32507909725… google · argon2026h2
Subject: docs.example.staging.plesk.tech
Issuer: Amazon RSA 2048 M02
SANs: docs.example.staging.plesk.tech
Valid: 2025-06-29 00:00:00 → 2026-07-28 23:59:59
83b64107a498a2aa… google · argon2026h2
Subject: docs.example.staging.plesk.tech
Issuer: Amazon RSA 2048 M02
SANs: docs.example.staging.plesk.tech
Valid: 2025-06-29 00:00:00 → 2026-07-28 23:59:59
04a3c32507909725… digicert · wyvern2026h2
Subject: docs.example.staging.plesk.tech
Issuer: Amazon RSA 2048 M02
SANs: docs.example.staging.plesk.tech
Valid: 2025-06-29 00:00:00 → 2026-07-28 23:59:59
83b64107a498a2aa… google · xenon2026h2
Subject: docs.example.staging.plesk.tech
Issuer: Amazon RSA 2048 M02
SANs: docs.example.staging.plesk.tech
Valid: 2025-06-29 00:00:00 → 2026-07-28 23:59:59

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
A 3.173.161.6 2026-06-01 01:36:51.488 2026-06-01 01:36:51.488
A 3.173.161.11 2026-06-01 01:36:51.488 2026-06-01 01:36:51.488
A 3.173.161.3 2026-06-01 01:36:51.488 2026-06-01 01:36:51.488
A 3.173.161.79 2026-06-01 01:36:51.488 2026-06-01 01:36:51.488
A 52.222.214.20 2026-06-01 02:10:56.456 2026-06-01 02:10:56.456
A 52.222.214.102 2026-06-01 02:10:56.456 2026-06-01 02:10:56.456
A 52.222.214.83 2026-06-01 02:10:56.456 2026-06-01 02:10:56.456
A 52.222.214.125 2026-06-01 02:10:56.456 2026-06-01 02:10:56.456