Domain

code.visualstudio.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of code.visualstudio.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

—

seen in DNS

Observed Certs

—

in our scans

DNS Records

13.107.213.65, 13.107.226.38, 13.107.226.43, 13.107.226.67, 13.107.246.65, 13.107.253.38, 13.107.253.43, 13.107.253.67

AAAA

2603:1061:14:133::1, 2603:1061:14:135::1, 2603:1061:14:137::1, 2603:1061:14:174::1, 2603:1061:14:20::1, 2603:1061:14:21::1, 2603:1061:14:22::1, 2603:1061:14:23::1

—

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.

117.72.17.101:80 href · ×6

106.52.213.94:80 href · ×5

43.161.250.143:443 href · ×4

165.227.32.99:80 href · ×3

47.237.200.84:993 href · ×3

117.72.99.25:80 href · ×3

47.79.226.18:443 href · ×3

42.192.39.170:443 href · ×2

106.14.16.106:443 href · ×2

198.200.36.51:80 href · ×2

141.62.116.77:443 href · ×2

47.100.231.192:443 href · ×2

23.236.68.174:5000 href · ×2

192.99.6.34:443 href · ×2

146.190.93.154:443 href · ×2

115.190.203.78:80 href · ×2

52.203.20.136:443 href · ×2

168.138.208.253:443 href · ×2

47.107.65.191:80 href · ×2

198.200.36.51:443 href · ×2

114.132.240.42:8081 href · ×2

149.102.140.197:443 href · ×2

192.53.120.188:443 href · ×2

83.229.123.238:443 href · ×2

168.138.208.253:80 href · ×2

20.198.216.94:443 href · ×2

152.136.98.75:443 href · ×2

167.71.64.151:443 href · ×2

133.18.122.207:8080 href · ×1

101.37.28.178:8888 href · ×1

157.230.187.166:80 href · ×1

47.253.250.150:80 href · ×1

43.130.3.12:443 href · ×1

192.9.228.171:8080 href · ×1

163.41.112.87:443 href · ×1

101.42.45.45:443 href · ×1

123.206.118.105:80 href · ×1

162.250.116.136:443 href · ×1

121.4.203.117:8080 href · ×1

34.123.79.215:443 href · ×1

47.109.23.206:443 href · ×1

216.92.84.243:443 href · ×1

39.105.186.182:80 href · ×1

154.21.201.155:8080 href · ×1

52.170.56.153:443 href · ×1

192.248.148.119:443 href · ×1

116.252.76.157:8081 href · ×1

152.136.98.75:80 href · ×1

60.168.145.236:80 href · ×1

133.18.122.207: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.