gitlab.cn
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of gitlab.cn
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 |
|---|---|---|
| about3s.gitlab.cn | 2026-05-26 15:53:54.251 | |
| coderider.gitlab.cn | 2026-06-22 20:24:02.994 | |
| devops.gitlab.cn | 2026-07-22 05:37:21.200 | |
| forum.gitlab.cn | 1970-01-01 00:00:00.000 | |
| gitlab.cn | 2026-07-28 03:24:34.002 | |
| image.email.gitlab.cn | 1970-01-01 00:00:00.000 | |
| perf.1k.gitlab.cn | 1970-01-01 00:00:00.000 | |
| release.gitlab.cn | 2026-07-20 19:47:19.513 |
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
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 |
|---|---|---|---|
| NS | dns11.hichina.com | 2026-06-03 22:21:28.970 | 2026-06-22 21:32:16.327 |
| MX | 10 mx2.qiye.aliyun.com | 2026-06-03 22:21:28.970 | 2026-07-28 03:24:34.002 |
| A | 212.129.158.239 | 2026-06-03 22:21:28.970 | 2026-07-28 03:24:34.002 |
| TXT | v=spf1 include:spf.qiye.aliyun.com -all | 2026-06-03 22:21:28.970 | 2026-07-28 03:24:34.002 |
| MX | 5 mx1.qiye.aliyun.com | 2026-06-03 22:21:28.970 | 2026-07-28 03:24:34.002 |
| NS | dns12.hichina.com | 2026-06-03 22:21:28.970 | 2026-06-22 21:32:16.327 |
| MX | 15 mx3.qiye.aliyun.com | 2026-06-03 22:21:28.970 | 2026-07-28 03:24:34.002 |
| NS | vip3.alidns.com | 2026-06-25 20:05:56.415 | 2026-07-28 03:24:34.002 |
| NS | vip4.alidns.com | 2026-06-25 20:05:56.415 | 2026-07-28 03:24:34.002 |