Check-Host.cc

Domain

api.relive.cc

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

Run a live full scan of api.relive.cc

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
18.239.50.102, 18.239.50.109, 18.239.50.77, 18.239.50.84, 3.171.214.105, 3.171.214.114, 3.171.214.77, 3.171.214.83
AAAA
2600:9000:20ab:4800:c:3a5d:d6c0:93a1, 2600:9000:20ab:5c00:c:3a5d:d6c0:93a1, 2600:9000:20ab:7200:c:3a5d:d6c0:93a1, 2600:9000:20ab:7c00:c:3a5d:d6c0:93a1, 2600:9000:20ab:800:c:3a5d:d6c0:93a1, 2600:9000:20ab:8400:c:3a5d:d6c0:93a1, 2600:9000:20ab:be00:c:3a5d:d6c0:93a1, 2600:9000:20ab:f600:c:3a5d:d6c0:93a1
MX
NS
TXT
v=spf1 -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: *.api.relive.cc
Issuer: Amazon RSA 2048 M01
SANs: *.api.relive.cc, api.relive.cc
Subject: *.api.relive.cc
Issuer: Amazon RSA 2048 M01
SANs: *.api.relive.cc, api.relive.cc
Subject: *.api.relive.cc
Issuer: Amazon RSA 2048 M01
SANs: *.api.relive.cc, api.relive.cc
Subject: *.api.relive.cc
Issuer: Amazon RSA 2048 M01
SANs: *.api.relive.cc, api.relive.cc

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.