Domain

technet.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 technet.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.226.38, 13.107.226.43, 13.107.226.67, 13.107.226.72, 13.107.253.38, 13.107.253.43, 13.107.253.67, 13.107.253.72

AAAA

2603:1061:14:133::1, 2603:1061:14:134::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

—

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.

218.38.161.191:80 href · ×4

172.237.30.215:80 href · ×3

128.27.75.66:8080 href · ×3

172.237.30.53:443 href · ×2

159.203.88.222:443 href · ×2

172.237.21.17:80 href · ×2

192.254.76.245:443 href · ×2

153.192.43.52:8081 href · ×2

183.97.156.161:8080 href · ×2

220.88.162.201:8080 href · ×2

173.233.95.84:443 href · ×2

66.187.70.26:443 href · ×2

222.108.163.98:8081 href · ×2

220.126.3.154:80 href · ×2

153.198.176.190:8080 href · ×2

45.63.48.139:443 href · ×2

118.38.199.116:80 href · ×2

58.239.217.136:80 href · ×2

172.235.35.88:443 href · ×2

104.200.214.220:80 href · ×2

168.126.202.62:8000 href · ×2

211.198.160.213:8080 href · ×2

52.156.129.44:443 href · ×2

59.3.53.104:80 href · ×2

14.63.220.142:443 href · ×2

172.239.68.129:443 href · ×2

121.143.69.184:80 href · ×2

172.237.79.78:443 href · ×1

71.95.100.130:80 href · ×1

172.237.71.132:443 href · ×1

111.234.141.8:8081 href · ×1

173.198.18.198:8088 href · ×1

172.237.27.98:80 href · ×1

210.101.69.213:8081 href · ×1

172.237.79.100:80 href · ×1

165.229.201.22:80 href · ×1

85.214.225.141:443 href · ×1

88.70.71.65:8081 href · ×1

59.0.77.222:8081 href · ×1

190.187.168.26:80 href · ×1

190.187.185.11:80 href · ×1

27.78.182.128:80 href · ×1

134.41.204.39:8000 href · ×1

172.235.35.232:443 href · ×1

220.86.41.56:80 href · ×1

165.229.201.69:80 href · ×1

175.205.152.72:80 href · ×1

60.39.58.102:8081 href · ×1

172.237.21.247:443 href · ×1

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

CT-Log Evidence

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

74155229ca6a4d65… google · xenon2026h2