Check-Host.cc

Domain

q.computer

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

Run a live full scan of q.computer

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

DNS Records

A
172.234.212.77, 172.236.103.15, 172.239.193.194
AAAA
MX
NS
ns1-coming-soon.sav.com, ns2-coming-soon.sav.com
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

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

Subdomain Resolves to Last seen
q.computer 2026-06-17 23:32:58.334
sananea.q.computer 2026-06-19 00:04:13.952
api.q.computer
1970-01-01 00:00:00.000
blog.q.computer
1970-01-01 00:00:00.000
cdn.q.computer
1970-01-01 00:00:00.000
ftp.q.computer
1970-01-01 00:00:00.000
json.q.computer
1970-01-01 00:00:00.000
mail.q.computer
1970-01-01 00:00:00.000
media.q.computer
1970-01-01 00:00:00.000
mobile.q.computer
1970-01-01 00:00:00.000
old.q.computer
1970-01-01 00:00:00.000
prod.q.computer
1970-01-01 00:00:00.000
v2.q.computer
1970-01-01 00:00:00.000
webmail.q.computer
1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

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

TLS Certificates

Subject: api.colonq.computer
Issuer: YE2
SANs: api.colonq.computer
Subject: colonq.computer
Issuer: YR2
SANs: colonq.computer

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

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 172.234.212.77 2026-06-17 23:32:58.334 2026-06-17 23:32:58.334
NS ns2-coming-soon.sav.com 2026-06-17 23:32:58.334 2026-06-17 23:32:58.334
NS ns1-coming-soon.sav.com 2026-06-17 23:32:58.334 2026-06-17 23:32:58.334
A 172.239.193.194 2026-06-17 23:32:58.334 2026-06-17 23:32:58.334
A 172.236.103.15 2026-06-17 23:32:58.334 2026-06-17 23:32:58.334