Domain

msdn.microsoft.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 msdn.microsoft.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.42, 13.107.226.43, 13.107.226.44, 13.107.226.45, 13.107.226.53, 13.107.226.67

AAAA

2603:1061:14:133::1, 2603:1061:14:134::1, 2603:1061:14:135::1, 2603:1061:14:137::1, 2603:1061:14:171::1, 2603:1061:14:174::1, 2603:1061:14:1c2::1, 2603:1061:14:20::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.56.14.51:80 href · ×4

166.252.108.195:80 href · ×4

175.214.171.38:80 href · ×4

96.3.49.27:80 href · ×4

24.149.76.115:80 href · ×4

74.218.98.26:80 href · ×4

175.213.64.213:80 href · ×4

46.77.71.213:80 href · ×4

166.252.1.11:80 href · ×4

74.208.223.129:8443 href · ×4

59.2.31.177:80 href · ×4

73.199.9.153:80 href · ×4

39.120.71.214:80 href · ×4

24.105.231.210:80 href · ×4

166.166.135.57:80 href · ×4

24.144.35.9:80 href · ×4

47.32.100.117:80 href · ×4

87.128.61.29:8000 href · ×4

121.149.55.89:80 href · ×4

59.26.184.150:80 href · ×4

131.148.61.41:80 href · ×4

166.168.244.133:80 href · ×4

175.213.64.183:80 href · ×4

174.106.165.175:80 href · ×4

166.166.177.233:80 href · ×4

98.243.44.22:80 href · ×4

72.215.131.228:80 href · ×4

173.12.51.92:80 href · ×4

211.216.161.157:80 href · ×4

109.195.18.49:443 href · ×4

23.114.111.9:80 href · ×4

121.163.100.74:80 href · ×4

172.237.30.215:80 href · ×3

104.131.172.42:443 href · ×3

166.252.109.57:80 href · ×2

129.186.168.173:8080 href · ×2

172.235.35.88:443 href · ×2

119.159.242.165:8443 href · ×2

172.237.30.53:443 href · ×2

166.252.108.158:80 href · ×2

61.91.121.5:8443 href · ×2

166.249.132.116:80 href · ×2

217.182.25.190:8443 href · ×2

62.243.46.139:8443 href · ×2

140.190.5.123:80 href · ×2

166.145.54.215:80 href · ×2

66.55.192.35:80 href · ×2

69.204.73.72:80 href · ×2

92.180.159.123:80 href · ×2

166.168.244.100:80 href · ×2

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

33d25147f799a5ae… google · xenon2026h2

Subject: msdn.microsoft.com

Issuer: Microsoft TLS G2 RSA CA OCSP 16

SANs: msdn.microsoft.com

Valid: 2026-02-01 03:54:04 → 2026-07-31 03:54:04

239fab576eb0692b… sectigo · elephant2026h1

Subject: msdn.microsoft.com