Check-Host.cc

Domain

brick.so

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

Run a live full scan of brick.so

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

DNS Records

A
31.43.160.6, 31.43.161.6
AAAA
MX
1 smtp.google.com
NS
ns-1209.awsdns-23.org, ns-2044.awsdns-63.co.uk, ns-28.awsdns-03.com, ns-852.awsdns-42.net
TXT
"_cf-custom-hostname.trust.brick.so, =3a22c704-1504-4a0e-bdc6-642447e5c708", MS=714DF4AB612E9754965303D014DC865F3C301798, google-site-verification=ARXhnDna5-LzDunkXJY7Q3b5uhyn7GcArpBqOQovT9o, v=spf1 include:_spf.google.com include:24242012.spf02.hubspotemail.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.

Subdomain Resolves to Last seen
form.porto.brick.so 2026-06-24 02:47:14.451
www.form.brick.so 2026-06-24 02:47:14.451
form.brick.so 2026-06-24 02:47:14.451
api.quarry.brick.so 2026-05-26 21:38:20.141
gateway.thalamus.brick.so 2026-05-27 15:47:07.611
quarry.brick.so 2026-05-26 21:38:20.141
thalamus.brick.so 2026-05-27 15:47:07.611
brick.so 2026-06-03 16:16:07.471
www.brick.so 2026-06-15 13:26:28.533
alcantara.brick.so
1970-01-01 00:00:00.000
api.arga.brick.so
1970-01-01 00:00:00.000
api.dev.brick.so
1970-01-01 00:00:00.000
api.panela1.retro.brick.so
1970-01-01 00:00:00.000
api.porto.brick.so
1970-01-01 00:00:00.000
api.victor.brick.so
1970-01-01 00:00:00.000
app.brick.so
1970-01-01 00:00:00.000
app.dev.brick.so
1970-01-01 00:00:00.000
app.porto.brick.so
1970-01-01 00:00:00.000
app.victor.brick.so
1970-01-01 00:00:00.000
app2.brick.so
1970-01-01 00:00:00.000
arga.brick.so
1970-01-01 00:00:00.000
dev.brick.so
1970-01-01 00:00:00.000
docs.victor.brick.so
1970-01-01 00:00:00.000
form.dev.brick.so
1970-01-01 00:00:00.000
form.panela1.retro.brick.so
1970-01-01 00:00:00.000
form2.brick.so
1970-01-01 00:00:00.000
gps.brick.so
1970-01-01 00:00:00.000
logs.brick.so
1970-01-01 00:00:00.000
logs.porto.brick.so
1970-01-01 00:00:00.000
monitor.panela1.retro.brick.so
1970-01-01 00:00:00.000
monitor.porto.brick.so
1970-01-01 00:00:00.000
movida.brick.so
1970-01-01 00:00:00.000
othertest.victor.brick.so
1970-01-01 00:00:00.000
porto.brick.so
1970-01-01 00:00:00.000
server.dev.brick.so
1970-01-01 00:00:00.000
victordocs.brick.so
1970-01-01 00:00:00.000
www.app.brick.so
1970-01-01 00:00:00.000
www.form.porto.brick.so
1970-01-01 00:00:00.000
www.gps.brick.so
1970-01-01 00:00:00.000
www.movida.brick.so
1970-01-01 00:00:00.000
www.porto.brick.so
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: thalamus.brick.so
Issuer: Amazon RSA 2048 M01
SANs: gateway.thalamus.brick.so, thalamus.brick.so
Subject: quarry.brick.so
Issuer: Amazon RSA 2048 M01
SANs: api.quarry.brick.so, quarry.brick.so

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.