langfuse.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of langfuse.com
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
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 |
|---|---|---|
| chat.langfuse.com | 2026-06-20 10:25:08.413 | |
| cloud.langfuse.com | 2026-07-25 04:05:18.930 | |
| atlantis.infra.langfuse.com | 2026-05-26 04:15:48.898 | |
| hipaa.cloud.langfuse.com | 2026-05-27 08:12:55.831 | |
| jp.cloud.langfuse.com | 2026-05-26 15:15:26.393 | |
| us.cloud.langfuse.com | 2026-05-26 03:15:29.400 | |
| api.reference.langfuse.com | 2026-06-20 03:55:00.937 | |
| aws-test.infra.langfuse.com | 1970-01-01 00:00:00.000 | |
| discord.langfuse.com | 1970-01-01 00:00:00.000 | |
| docs-snapshot.langfuse.com | 1970-01-01 00:00:00.000 | |
| docs.langfuse.com | 1970-01-01 00:00:00.000 | |
| get.langfuse.com | 1970-01-01 00:00:00.000 | |
| langfuse.com | 2026-07-20 17:28:25.223 | |
| ops.infra.langfuse.com | 1970-01-01 00:00:00.000 | |
| python.reference.langfuse.com | 1970-01-01 00:00:00.000 | |
| static.langfuse.com | 1970-01-01 00:00:00.000 | |
| www.langfuse.com | 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
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.