Check-Host.cc

Domain

s.buick.com

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

Run a live full scan of s.buick.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
4
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
3
in our scans

DNS Records

A
75.2.120.88, 99.83.235.193
AAAA
2600:9000:a413:6638:30bb:f9cc:3e3e:3eba, 2600:9000:a70e:eb29:ae3f:3baf:ae5c:8918
MX
NS
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

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

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

db6b6030ac6f57f5… google · argon2026h2
Subject: s.cadillac.com
Issuer: Amazon RSA 2048 M01
SANs: s.cadillac.com, s.buick.com, s.gm.financial, m.gm.financial, s.gmc.com, s.gm.com, energy.gm.com, cadillac.financial, s.chevy.com
Valid: 2025-09-23 00:00:00 → 2026-10-22 23:59:59
31b38104b1a9a0e4… google · argon2026h2
Subject: go.meta.me
Issuer: Amazon RSA 2048 M01
SANs: go.meta.me, epsonqr.com, go.fb.me, s.buick.com, s.gmc.com, energy.gm.com, s.cadillac.com, s.gm.com, kotex-my.com, huggies-it.com
Valid: 2025-09-22 00:00:00 → 2026-10-21 23:59:59
86e8399e4067b8f7… google · argon2026h2
Subject: go.meta.me
Issuer: Amazon RSA 2048 M01
SANs: go.meta.me, epsonqr.com, go.fb.me, s.buick.com, s.gmc.com, energy.gm.com, s.cadillac.com, s.gm.com, kotex-my.com, huggies-it.com
Valid: 2025-09-22 00:00:00 → 2026-10-21 23:59:59

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.