Check-Host.cc

Domain

acst.app

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

Run a live full scan of acst.app

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
108.138.26.110, 108.138.26.128, 108.138.26.15, 108.138.26.87, 3.173.161.128, 3.173.161.3, 3.173.161.33, 3.173.161.87
AAAA
2600:9000:2491:5000:8:7516:d540:93a1, 2600:9000:2491:5400:8:7516:d540:93a1, 2600:9000:2491:7000:8:7516:d540:93a1, 2600:9000:2491:8a00:8:7516:d540:93a1, 2600:9000:2491:9c00:8:7516:d540:93a1, 2600:9000:2491:c600:8:7516:d540:93a1, 2600:9000:2491:e200:8:7516:d540:93a1, 2600:9000:2491:ec00:8:7516:d540:93a1
MX
21 route3.mx.cloudflare.net, 76 route1.mx.cloudflare.net, 95 route2.mx.cloudflare.net
NS
dora.ns.cloudflare.com, rick.ns.cloudflare.com
TXT
google-site-verification=_Gfe3ylDGem1Y0GIYI4vTiEKt6IgQ-6yN70UIRO-iN4, v=spf1 include:_spf.mx.cloudflare.net ~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

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

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.