Check-Host.cc

Domain

steemit.com

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

Run a live full scan of steemit.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
10
A/AAAA targets
Subdomains
19
CT + scan + body
Record Types
5
seen in DNS
Observed Certs
10
in our scans

DNS Records

A
104.21.25.160, 172.67.134.94
AAAA
2606:4700:3030::6815:19a0, 2606:4700:3031::ac43:865e, 2606:4700:3032::ac43:865e, 2606:4700:3033::6815:19a0
MX
1 aspmx.l.google.com, 10 aspmx2.googlemail.com, 10 aspmx3.googlemail.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
charles.ns.cloudflare.com, zara.ns.cloudflare.com
TXT
Sendinblue-code:f5a05ffddc5768c1528c46adac114118, atlassian-domain-verification=3+D0MLQcO5ypQwuiE3at1EAJsxzbBRe/cjBvQ+z+wojfYvoUibmIObXyVeQ8lr3G, brave-ledger-verification=5cf9d6f36f996492f468ef8cdb8083625b3cb9bac93316bafd7b0c365ec917bb, google-site-verification=Dq27ZCigWKSuNEyKx6hXFdhc2xtFh1jjX8b96wIPU3w, v=spf1 include:_spf.google.com ~all
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

Subject: steemit.com
Issuer: Amazon RSA 2048 M02
SANs: *.steemit.com, steemit.com
Subject: steemit.com
Issuer: Amazon RSA 2048 M02
SANs: *.steemit.com, steemit.com

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.