Check-Host.cc

Domain

mail.microsoft

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

Run a live full scan of mail.microsoft

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
AAAA
MX
NS
ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns3-36.azure-dns.org, ns4-36.azure-dns.info
TXT
v=spf1 -all
CNAME
CAA
0 contactemail "caarecordaware@microsoft.com"

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

Subject: SharePoint_webmail.microsoft.corp
Issuer: Domain Controller Certificate
SANs: SharePoint_webmail.microsoft.corp
Subject: cloud.email.microsoftonline.com
Issuer: Microsoft Azure RSA TLS Issuing CA 08
SANs: cloud.email.microsoftonline.com
Subject: mail.microsoftho.me
Issuer: R12
SANs: mail.microsoftho.me
Subject: accountemail.microsoft.com
Issuer: Microsoft TLS G2 RSA CA OCSP 04
SANs: accountemail.microsoft.com, m.accountemail.microsoft.com, res.accountemail.microsoft.com, t.accountemail.microsoft.com
Subject: accountemail.microsoft.com
Issuer: Microsoft TLS G2 RSA CA OCSP 04
SANs: accountemail.microsoft.com, m.accountemail.microsoft.com, res.accountemail.microsoft.com, t.accountemail.microsoft.com

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.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
TXT v=spf1 -all 2026-06-05 18:02:09.481 2026-07-15 20:04:13.980
NS ns1-36.azure-dns.com 2026-06-05 18:02:09.481 2026-07-15 20:04:13.980
NS ns4-36.azure-dns.info 2026-06-05 18:02:09.481 2026-07-15 20:04:13.980
NS ns3-36.azure-dns.org 2026-06-05 18:02:09.481 2026-07-15 20:04:13.980
CAA 0 contactemail "caarecordaware@microsoft.com" 2026-06-05 18:02:09.481 2026-07-15 20:04:13.980
NS ns2-36.azure-dns.net 2026-06-05 18:02:09.481 2026-07-15 20:04:13.980