Domain

blogs.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 blogs.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.42, 13.107.226.43, 13.107.226.44, 13.107.226.53, 13.107.226.67, 13.107.226.72, 13.107.246.65

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:1c2::1, 2603:1061:14:20::1, 2603:1061:14:21::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.

82.223.83.197:443 href · ×3

104.254.246.89:80 href · ×2

82.223.11.66:443 href · ×2

212.227.228.97:443 href · ×2

82.223.39.185:80 href · ×2

82.223.27.232:80 href · ×2

82.223.108.102:443 href · ×2

82.223.68.30:80 href · ×2

82.223.39.187:443 href · ×2

82.223.28.148:80 href · ×2

82.223.83.197:80 href · ×2

74.208.211.82:443 href · ×2

108.175.10.36:443 href · ×2

104.214.102.198:80 href · ×2

74.208.88.63:80 href · ×2

70.35.203.184:443 href · ×2

82.223.30.176:443 href · ×2

82.223.111.30:80 href · ×2

79.137.61.10:80 href · ×2

34.240.87.59:443 href · ×2

82.223.68.116:80 href · ×2

82.223.111.23:443 href · ×2

82.223.39.37:80 href · ×2

82.223.39.236:80 href · ×2

74.208.28.226:80 href · ×2

82.223.222.211:443 href · ×2

82.223.0.45:443 href · ×2

213.99.41.61:80 href · ×2

82.223.12.29:443 href · ×2

82.223.70.176:80 href · ×2

35.188.189.79:443 href · ×2

82.223.2.83:80 href · ×2

82.223.35.162:443 href · ×2

217.160.225.98:80 href · ×2

91.67.106.235:80 href · ×2

139.59.169.82:443 href · ×2

139.99.219.239:443 href · ×1

82.223.197.150:80 href · ×1

82.223.9.55:443 href · ×1

91.62.178.116:80 href · ×1

54.232.81.120:80 href · ×1

82.223.101.34:80 href · ×1

178.190.155.7:80 href · ×1

212.227.226.224:443 href · ×1

217.160.225.116:443 href · ×1

104.192.4.126:80 href · ×1

87.176.91.12:80 href · ×1

74.208.81.144:80 href · ×1

5.44.96.118:443 href · ×1

3.11.215.189:80 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.

f4f34ce362569f44… google · xenon2026h2

Subject: blogs.msdn.microsoft.com

Issuer: Microsoft TLS G2 RSA CA OCSP 04