Check-Host.cc

Try 1.1.1.1 AS13335 check-host.cc /country/de /tld/cc
Domain

techcommunity.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 techcommunity.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

A
150.171.109.101, 150.171.109.198, 150.171.109.34, 150.171.109.35, 150.171.109.36, 150.171.109.51, 150.171.109.53, 150.171.110.52
AAAA
2603:1061:14:133::1, 2603:1061:14:135::1, 2603:1061:14:137::1, 2603:1061:14:21::1, 2603:1061:14:22::1, 2603:1061:14:23::1, 2603:1061:14:32::1, 2603:1061:14:34::1
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

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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.

c71ab4eeecf3350b… google · xenon2026h2
Subject: techcommunity.microsoft.com
Issuer: Microsoft TLS G2 RSA CA OCSP 04
SANs: techcommunity.microsoft.com
Valid: 2026-02-24 20:07:02 → 2026-08-23 20:07:02
6823b3f560f59710… google · xenon2026h2
Subject: techcommunity.microsoft.com
Issuer: Microsoft Azure RSA TLS Issuing CA 07
SANs: techcommunity.microsoft.com
Valid: 2026-02-21 19:53:42 → 2026-08-20 19:53:42
a4fd20cb81c4af39… google · argon2026h2
Subject: ak-secure01.microsoft.com
Issuer: Microsoft TLS G2 ECC CA OCSP 06
SANs: techcommunity.microsoft.com, network.officeppe.com, ak-secure01.microsoft.com
Valid: 2025-12-23 18:53:18 → 2026-12-18 18:53:18
e3639be631a2a284… google · argon2026h2
Subject: ak-secure01.microsoft.com
Issuer: Microsoft TLS G2 ECC CA OCSP 06
SANs: techcommunity.microsoft.com, network.officeppe.com, ak-secure01.microsoft.com
Valid: 2025-12-23 18:53:18 → 2026-12-18 18:53:18
a4fd20cb81c4af39… google · xenon2026h2
Subject: ak-secure01.microsoft.com
Issuer: Microsoft TLS G2 ECC CA OCSP 06
SANs: techcommunity.microsoft.com, network.officeppe.com, ak-secure01.microsoft.com
Valid: 2025-12-23 18:53:18 → 2026-12-18 18:53:18
e3639be631a2a284… google · xenon2026h2
Subject: ak-secure01.microsoft.com
Issuer: Microsoft TLS G2 ECC CA OCSP 06
SANs: techcommunity.microsoft.com, network.officeppe.com, ak-secure01.microsoft.com
Valid: 2025-12-23 18:53:18 → 2026-12-18 18:53:18

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.