githubstatus.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of githubstatus.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 |
|---|---|---|
| eu.githubstatus.com | 2026-07-20 11:02:17.624 | |
| www.githubstatus.com | 2026-07-18 16:49:51.521 | |
| githubstatus.com | 2026-07-28 19:31:00.676 | |
| jp.githubstatus.com | 2026-06-16 22:59:17.418 | |
| us.githubstatus.com | 2026-06-24 02:35:12.536 |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
IPs Citing This Domain
Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.
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.
| Origin IP | Origin ASN | CDN ASN | Confidence | Reasoning |
|---|---|---|---|---|
| 132.145.114.136 | AS31898 | AS54113 | 95% | cert 3e37d509… served by 132.145.114.136 (AS31898) carries SAN githubstatus.com which currently resolves through Fastly (AS54113) at 185.199.110.153, 185.199.111.153, 185.199.109.153, 185.199.108.153 |
CT-Log Evidence
Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.
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.