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.
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
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 |
|---|---|---|---|
| A | 185.199.109.153 | 2026-05-25 21:56:50.553 | 2026-07-28 19:31:00.676 |
| A | 185.199.108.153 | 2026-05-25 21:56:50.553 | 2026-07-28 19:31:00.676 |
| A | 185.199.111.153 | 2026-05-25 21:56:50.553 | 2026-07-28 19:31:00.676 |
| A | 185.199.110.153 | 2026-05-25 21:56:50.553 | 2026-07-28 19:31:00.676 |
| TXT | atlassian-domain-verification=ZVs1DUhbi0a2zZz8C19vh6F4j0Yxe13LOaDHKlxNY3i7aurf/lfmO9sbabibe99z | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| CAA | 0 issue "sectigo.com" | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | dns4.p04.nsone.net | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| TXT | v=spf1 include:stspg-customer.com -all | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | ns-1962.awsdns-53.co.uk | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | ns-613.awsdns-12.net | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| TXT | status-page-domain-verification=30gcnw2xxnb0 | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | ns-1330.awsdns-38.org | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | dns1.p04.nsone.net | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | ns-64.awsdns-08.com | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | dns2.p04.nsone.net | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| TXT | google-site-verification=Ig58Ca-M8wZTtmZqN0Q5tgZlifdgrNu7IzOZzVASqZs | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| CAA | 0 issue "letsencrypt.org" | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |
| NS | dns3.p04.nsone.net | 2026-05-26 00:17:38.499 | 2026-07-28 19:31:00.676 |