HOW.IS
?

How is office365.com?

Looks fine risk 0/100

Registered 21 years ago, on no blocklists we checked, valid HTTPS, the site answered 403 in 42 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How office365.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
403
42 ms
HTTPS
87 d
left on a Microsoft Corporation certificate
Age
21 years
registered 2005-06-20
Blocklists
0
listings across 4 lists; 1 did not answer

Everything we looked at

DNS records4 record types
A20.119.0.28
40.112.243.53
NSns1-07.azure-dns.com
ns3-07.azure-dns.org
ns4-07.azure-dns.info
ns2-07.azure-dns.net
TXT_ufamlucd6jp7xslb9wnr85vc03dxyqh
officeprodes.azurewebsites.net
google-site-verification=u9PqvuplbTIYlwiMAzJWnRRtHYoAlaTX5GMtRRXqWXA
v=spf1 include:spf.protection.outlook.com ~all
CAA{'type': 'CAA', 'critical': 0, 'contactemail': 'caarecordaware@microsoft.com'}
{'type': 'CAA', 'iodef': 'mailto:domains@microsoft.com', 'critical': 0}
{'type': 'CAA', 'issue': 'digicert.com', 'critical': 0}
{'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0}
{'type': 'CAA', 'issue': 'microsoft.com', 'critical': 0}
RegistrationMarkMonitor Inc.
registrarMarkMonitor Inc.
registered2005-06-20
expires2027-06-20
last changed2026-05-19
ownerMicrosoft Corporation
nameserversns1-07.azure-dns.com
ns2-07.azure-dns.net
ns3-07.azure-dns.org
ns4-07.azure-dns.info
statusclient delete prohibited
client transfer prohibited
client update prohibited
server delete prohibited
server transfer prohibited
server update prohibited
registered 2005-06-20expires 2027-06-20
HTTPS certificate87 days left
validyes
issuerMicrosoft Corporation
coversteams.com, www.teams.com, office365.com, www.office365.com, o365.com, www.o365.com, akaoffice-ame.trafficmanager.net, akaoffice.trafficmanager.net
protocolTLSv1.3
issued 2026-10-13expires 2027-01-21
DNSSECsecure

Domain is properly signed — chain validated by an independent validating resolver

. → com → office365.com
Email authenticationfair
SPFpass v=spf1 include:spf.protection.outlook.com ~all
DMARCpass policy reject
DKIMnone of 1 common selectors

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade B · 165/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
45/45missing: DKIM Presence
Advanced Security
5/25missing: Mail Server Configuration, SOA Record Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop20.119.0.28Barracuda20.119.0.28UCEPROTECT Level 120.119.0.28SpamCop40.112.243.53Barracuda40.112.243.53UCEPROTECT Level 140.112.243.53

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.

curl "https://how.is/v1/domain/trust?domain=office365.com" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=office365.com"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on office365.com. Reference: /llms.txt.

Watch office365.com. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.

Watch — $1 / 30 days