Check-Host.cc

Domain

local.express

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

Run a live full scan of local.express

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
47
A/AAAA targets
Subdomains
158
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
6
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

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

Subject: startprinters.stage.local.express
Issuer: Amazon RSA 2048 M01
SANs: startprinters.stage.local.express
Subject: startprinters.stage.local.express
Issuer: Amazon RSA 2048 M01
SANs: startprinters.stage.local.express
Subject: customer.agents.stage.local.express
Issuer: Amazon RSA 2048 M04
SANs: customer.agents.stage.local.express
Subject: *.dev.infra.local.express
Issuer: Amazon RSA 2048 M04
SANs: *.dev.infra.local.express
Subject: startprinters.stage.local.express
Issuer: Amazon RSA 2048 M01
SANs: startprinters.stage.local.express
Subject: fusion-parser-staging.infra.local.express
Issuer: E8
SANs: fusion-parser-staging.infra.local.express
Subject: *.dev.infra.local.express
Issuer: Amazon RSA 2048 M04
SANs: *.dev.infra.local.express
Subject: *.dev.infra.local.express
Issuer: Amazon RSA 2048 M04
SANs: *.dev.infra.local.express
Subject: ftp.stage.local.express
Issuer: ftp.stage.local.express
SANs: ftp.stage.local.express
Subject: *.stage.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.stage.local.express
Subject: agents.dev.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.agents.dev.local.express, agents.dev.local.express
Subject: *.stage.infra.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.stage.infra.local.express
Subject: *.dev.infra.local.express
Issuer: Amazon RSA 2048 M04
SANs: *.dev.infra.local.express
Subject: startprinters.dev.local.express
Issuer: Amazon RSA 2048 M01
SANs: startprinters.dev.local.express
Subject: agents.dev.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.agents.dev.local.express, agents.dev.local.express
Subject: *.stage.infra.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.stage.infra.local.express
Subject: n8n.stage.infra.local.express
Issuer: Amazon RSA 2048 M04
SANs: n8n.stage.infra.local.express
Subject: *.stage.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.stage.local.express
Subject: *.prod.infra.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.prod.infra.local.express
Subject: customer.agents.stage.local.express
Issuer: Amazon RSA 2048 M04
SANs: customer.agents.stage.local.express
Subject: *.prod.infra.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.prod.infra.local.express
Subject: *.stage.local.express
Issuer: Amazon RSA 2048 M01
SANs: *.stage.local.express
Subject: customer.agents.stage.local.express
Issuer: Amazon RSA 2048 M04
SANs: customer.agents.stage.local.express

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.

4b9d75a401cca949… google · argon2026h2
Subject: local.express
Issuer: Amazon RSA 2048 M01
SANs: local.express, *.dev.local.express, *.local.express, *.stage.local.express
Valid: 2025-11-13 00:00:00 → 2026-12-11 23:59:59
4b9d75a401cca949… cloudflare · nimbus2026
Subject: local.express
Issuer: Amazon RSA 2048 M01
SANs: local.express, *.dev.local.express, *.local.express, *.stage.local.express
Valid: 2025-11-13 00:00:00 → 2026-12-11 23:59:59

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
NS ns-cloud-c1.googledomains.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
TXT v=spf1 include:spf.mandrillapp.com include:_spf.google.com include:_spf.freshsales.io include:servers.mcsv.net ~all 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
A 18.216.168.124 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
NS ns-cloud-c3.googledomains.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
TXT MS=ms52111522 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
MX 5 alt2.aspmx.l.google.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
TXT facebook-domain-verification=atx7rhm2il1agd11imf9nni3ohj756 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
MX 10 alt4.aspmx.l.google.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
MX 1 aspmx.l.google.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
MX 5 alt1.aspmx.l.google.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
NS ns-cloud-c4.googledomains.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
MX 10 alt3.aspmx.l.google.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216
NS ns-cloud-c2.googledomains.com 2026-06-16 03:07:34.216 2026-06-16 03:07:34.216