Check-Host.cc

Domain

analytics.twitter.com

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

Run a live full scan of analytics.twitter.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
2
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

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.

77.40.52.83:443 href · ×3
195.201.146.157:8080 href · ×2
91.209.190.235:443 href · ×2
18.213.90.241:443 href · ×2
3.33.211.142:443 href · ×2
50.116.33.51:80 href · ×2
46.224.1.242:443 href · ×2
18.192.4.56:80 href · ×2
130.51.22.3:8080 href · ×2
157.245.55.182:8888 href · ×2
13.216.224.127:443 href · ×2
159.203.243.144:80 href · ×2
210.140.164.103:443 href · ×2
37.72.173.100:8080 href · ×2
192.227.248.210:443 href · ×2
141.94.22.58:443 href · ×2
92.118.59.7:8080 href · ×2
5.39.85.49:443 href · ×1
35.189.35.212:443 href · ×1
35.93.43.103:443 href · ×1
192.241.201.49:443 href · ×1
52.23.72.35:443 href · ×1
54.206.138.124:443 href · ×1
34.255.47.159:443 href · ×1
46.183.163.125:443 href · ×1
34.248.209.211:443 href · ×1
207.58.162.165:443 href · ×1
67.227.199.204:443 href · ×1
52.68.82.250:80 href · ×1
130.49.148.147:443 href · ×1
104.236.63.30:80 href · ×1
52.195.39.115:80 href · ×1
194.87.236.99:443 href · ×1
15.135.156.50:443 href · ×1
50.28.40.168:443 href · ×1
101.34.186.68:443 href · ×1
54.196.188.134:443 href · ×1
143.110.164.185:80 href · ×1
18.202.98.18:443 href · ×1
34.237.194.41:443 href · ×1
75.130.125.16:443 href · ×1
18.141.12.188:80 href · ×1
203.191.246.45:443 href · ×1
153.125.128.152:80 href · ×1
54.92.43.202:443 href · ×1
157.7.137.70:443 href · ×1
52.65.65.138:80 href · ×1
54.95.146.157:80 href · ×1
188.225.76.122:443 href · ×1
16.176.88.253:443 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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.