Check-Host.cc

Domain

st.com

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

Run a live full scan of st.com

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
217
A/AAAA targets
Subdomains
223
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
6
in our scans

DNS Records

A
54.194.135.49
AAAA
MX
10 st-com.mail.protection.outlook.com
NS
a1-23.akam.net, a2-66.akam.net, a28-66.akam.net, a5-64.akam.net, a8-66.akam.net, a9-65.akam.net, delta.dmz-ap.st.com, delta.dmz-eu.st.com
TXT
EL+b+HLOjUandS3GnT4aSMKKl+hEpYEba0apWnXH3FqPtQSOaZBda+ZakVW9rT05hN9wjSvzcUY3RfQemlAQ7g==, MS=ms37882190, MS=ms59221250, _globalsign-domain-verification=sbWhwwHtdnXMY_8oa_2AwroFfoc6imgOvFuDWHNoP0, atlassian-domain-verification=f3LTJ77zFUhFncMSteHljGP2BwYABw9ykWzPP08I7DFMy7gKAbOr7N5tc5SWGglC, cisco-ci-domain-verification=25dd1b4722f650b8c8d7cb3beb39c348fc90005fbed666c7e559ff0f7306decc, docker-verification=d6d198bc-8993-4f90-9414-e4febe3b4437, docusign=175308d5-aa3a-4d76-a827-b74155ac8e32
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.

Threat Intelligence

Domain threat-intel pending

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

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.