HOW.IS
?

How is bing.com?

Looks fine risk 0/100

Registered 31 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 129 ms.

Why

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

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

How bing.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
129 ms · ends at www.bing.com
HTTPS
91 d
left on a Microsoft Corporation certificate
Age
31 years
registered 1996-01-29
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records6 record types
A150.171.28.10
150.171.27.10
AAAA2620:1ec:33::10
2620:1ec:33:1::10
MX10 bing-com.mail.protection.outlook.com
NSdns4.p09.nsone.net
dns1.p09.nsone.net
ns2-204.azure-dns.net
ns3-204.azure-dns.org
dns2.p09.nsone.net
dns3.p09.nsone.net
ns1-204.azure-dns.com
ns4-204.azure-dns.info
TXTv=spf1 include:spf.protection.outlook.com -all
facebook-domain-verification=09yg8uzcfnqnlqekzsbwjxyy8rdck7
google-site-verification=SHuSHN0Hv3nwBI9So329KwfbQ7xLif64SRwcGSdWNAU
google-site-verification=OkRY8R261shK5B8uEwvsFZp9nQ2gRoHavGlruok1azc
v=msv1 t=6097A7EA-53F7-4028-BA76-6869CB284C54
CAA{'type': 'CAA', 'issue': 'microsoft.com', 'critical': 0}
{'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0}
{'type': 'CAA', 'issue': 'digicert.com', 'critical': 0}
{'type': 'CAA', 'critical': 0, 'contactemail': 'caarecordaware@microsoft.com'}
RegistrationMarkMonitor Inc.
registrarMarkMonitor Inc.
registered1996-01-29
expires2027-01-30
last changed2025-12-29
ownerMicrosoft Corporation
nameserversdns1.p09.nsone.net
dns2.p09.nsone.net
dns3.p09.nsone.net
dns4.p09.nsone.net
ns1-204.azure-dns.com
ns2-204.azure-dns.net
ns3-204.azure-dns.org
ns4-204.azure-dns.info
statusclient delete prohibited
client transfer prohibited
client update prohibited
server delete prohibited
server transfer prohibited
server update prohibited
registered 1996-01-29expires 2027-01-30
HTTPS certificate91 days left
validyes
issuerMicrosoft Corporation
covers*.platform.bing.com, *.bing.com, bing.com, ieonline.microsoft.com, *.api.bing.com, *.cn.bing.net, *.cn.bing.com, ssl-api.bing.com, *.api.bing.net, *.bingapis.com, feedback.microsoft.com, insertmedia.bing.office.net
protocolTLSv1.3
issued 2026-10-17expires 2027-01-25
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → bing.com
Email authenticationgood
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 A · 180/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
45/45missing: DKIM Presence
Advanced Security
20/25missing: Mail Server Configuration
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 8 lookups
SURBL MultidomainURIBL MultidomainSpamCop150.171.27.10Barracuda150.171.27.10UCEPROTECT Level 1150.171.27.10SpamCop150.171.28.10Barracuda150.171.28.10UCEPROTECT Level 1150.171.28.10

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=bing.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=bing.com"

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

Watch bing.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