Check-Host.cc

Domain

twitter.github.com

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

Run a live full scan of twitter.github.com

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
A/AAAA targets
Subdomains
CT + scan + body
Record Types
1
seen in DNS
Observed Certs
in our scans

DNS Records

A
AAAA
MX
NS
TXT
CNAME
CAA
0 issue "digicert.com", 0 issue "letsencrypt.org", 0 issue "sectigo.com", 0 issuewild "digicert.com", 0 issuewild "letsencrypt.org", 0 issuewild "sectigo.com"

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

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.

37.27.87.198:443 href · ×4
69.195.98.183:443 href · ×4
45.56.76.173:80 href · ×4
34.195.201.0:80 href · ×4
46.30.8.191:443 href · ×2
51.210.36.235:443 href · ×2
213.190.29.35:443 href · ×2
34.205.38.93:80 href · ×2
5.180.64.36:8081 href · ×2
117.74.64.89:80 href · ×2
88.218.225.152:8081 href · ×2
5.180.64.35:443 href · ×2
5.180.64.39:443 href · ×2
91.237.99.138:80 href · ×1
213.190.30.22:8081 href · ×1
34.229.39.118:443 href · ×1
216.92.244.184:443 href · ×1
52.29.6.93:80 href · ×1
193.142.42.104:443 href · ×1
213.190.29.46:443 href · ×1
88.218.225.153:443 href · ×1
192.64.190.51:80 href · ×1
162.243.149.181:80 href · ×1
5.180.65.36:443 href · ×1
5.180.64.46:8081 href · ×1
202.182.51.45:443 href · ×1
164.92.184.186:80 href · ×1
124.123.69.36:443 href · ×1
176.31.211.225:443 href · ×1
213.190.30.19:443 href · ×1
193.142.43.36:8081 href · ×1
91.205.184.98:443 href · ×1
54.201.251.29:443 href · ×1
194.48.170.197:443 href · ×1
135.125.114.171:443 href · ×1
167.172.186.255:443 href · ×1
85.214.63.141:80 href · ×1
104.131.91.248:443 href · ×1
193.142.42.105:443 href · ×1
5.9.156.24:80 href · ×1
209.121.135.35:443 href · ×1
161.35.203.50:80 href · ×1
88.218.225.156:8081 href · ×1
185.157.234.143:80 href · ×1
104.248.17.254:80 href · ×1
213.190.28.35:8081 href · ×1
157.7.164.148:443 href · ×1
149.210.212.194:8080 href · ×1
68.183.72.5:80 href · ×1
193.142.43.34:8081 href · ×1

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.

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
CAA 0 issue "sectigo.com" 2026-05-26 02:46:31.734 2026-07-23 09:10:34.818
CAA 0 issuewild "sectigo.com" 2026-05-26 02:46:31.734 2026-07-23 09:10:34.818
CAA 0 issuewild "digicert.com" 2026-05-26 02:46:31.734 2026-07-23 09:10:34.818
CAA 0 issue "digicert.com" 2026-05-26 02:46:31.734 2026-07-23 09:10:34.818
CAA 0 issuewild "letsencrypt.org" 2026-05-26 02:46:31.734 2026-07-23 09:10:34.818
CAA 0 issue "letsencrypt.org" 2026-05-26 02:46:31.734 2026-07-23 09:10:34.818