Check-Host.cc

Domain

segment.build

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

Run a live full scan of segment.build

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

DNS Records

A
AAAA
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

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
segment.build 2026-07-28 06:41:44.976
storybook.segment.build 2026-06-20 02:37:30.652
access.segment.build 2026-06-16 17:50:56.573
webhooks.euw1.segment.build 2026-07-24 19:10:21.723
unified-access.segment.build 2026-06-06 02:52:02.871
app.segment.build 2026-06-14 23:37:38.836
billing-dashboard.segment.build 2026-05-26 16:22:23.746
eu1.app.segment.build 2026-05-27 04:39:33.428
eu1.orion.segment.build 2026-05-27 16:34:03.150
flagon.use1.segment.build 2026-05-31 03:27:40.752
replay-check.euw1.segment.build 2026-05-26 05:39:17.045
objects-bulk-api.euw1.segment.build 2026-05-26 19:16:41.100
airflow.dataeng.segment.build
1970-01-01 00:00:00.000
airflow.datasci.segment.build
1970-01-01 00:00:00.000
armada-proxy.dataeng.segment.build
1970-01-01 00:00:00.000
armada.dataeng.segment.build
1970-01-01 00:00:00.000
cdn.edgefn.segment.build
1970-01-01 00:00:00.000
cdp.use1.segment.build
1970-01-01 00:00:00.000
engage-services-dev.segment.build
1970-01-01 00:00:00.000
engage-services-eu.segment.build
1970-01-01 00:00:00.000
engage.segment.build
1970-01-01 00:00:00.000
euw1.engage.segment.build
1970-01-01 00:00:00.000
euw1.segment.build
1970-01-01 00:00:00.000
fakestage.dev.segment.build
1970-01-01 00:00:00.000
iam.profiles.use1.segment.build
1970-01-01 00:00:00.000
nginx-internal.euw1.segment.build
1970-01-01 00:00:00.000
oauth.dataeng.segment.build
1970-01-01 00:00:00.000
preview.segment.build
1970-01-01 00:00:00.000
profiles.use1.segment.build
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

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.

9df438cd702850ec… cloudflare · nimbus2026
Subject: *.segment.build
Issuer: Amazon RSA 2048 M04
SANs: segment.build, *.segment.build
Valid: 2025-08-09 00:00:00 → 2026-09-07 23:59:59
8de464af26b8f9bb… cloudflare · nimbus2026
Subject: *.segment.build
Issuer: Amazon RSA 2048 M03
SANs: *.segment.build, segment.build
Valid: 2025-07-28 00:00:00 → 2026-08-26 23:59:59
cb5a40d4946c97a3… cloudflare · nimbus2026
Subject: *.segment.build
Issuer: Amazon RSA 2048 M03
SANs: *.segment.build, segment.build
Valid: 2025-07-28 00:00:00 → 2026-08-26 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.