How is bing.net?

Be careful risk 20/100

Registered 29 years ago, on no blocklists we checked, no valid HTTPS certificate, the site did not answer (SSLCertVerificationError).

Why

02050100

finecarefulhigh risk

+20No valid HTTPS certificate.

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

Site

down

SSLCertVerificationError

HTTPS

invalid

certificate not read

Age

29 years

registered 1997-09-03

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	204.79.197.200
NS	ns3-204.azure-dns.org ns4-204.azure-dns.info ns1-204.azure-dns.com dns4.p08.nsone.net dns3.p08.nsone.net ns2-204.azure-dns.net dns2.p08.nsone.net dns1.p08.nsone.net
TXT	AFDVALIDATION=Bing
CAA	{'type': 'CAA', 'issue': 'digicert.com', 'critical': 0} {'type': 'CAA', 'critical': 0, 'contactemail': 'caarecordaware@microsoft.com'} {'type': 'CAA', 'issue': 'microsoft.com', 'critical': 0} {'type': 'CAA', 'issue': 'globalsign.com', 'critical': 0}

RegistrationMarkMonitor Inc.

registrar	MarkMonitor Inc.
registered	1997-09-03
expires	2027-09-02
last changed	2026-08-01
owner	Microsoft Corporation
nameservers	dns1.p03.nsone.net dns2.p03.nsone.net dns3.p03.nsone.net dns4.p03.nsone.net ns1-204.azure-dns.com ns2-204.azure-dns.net ns3-204.azure-dns.org ns4-204.azure-dns.info
status	client delete prohibited client transfer prohibited client update prohibited

registered 1997-09-03expires 2027-09-02

HTTPS certificatenot valid

valid	no
issuer	Microsoft Corporation
covers	*.azureedge.net
protocol	TLSv1.3

issued 2026-10-27expires 2027-02-04

DNSSECinsecure

Domain is not signed with DNSSEC

. → net → bing.net

Email authenticationpoor

SPF	none
DMARC	none
DKIM	none of 1 common selectors

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

Security scoregrade C · 125/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

15/45missing: SPF Record, DMARC Record, DKIM Presence

Advanced Security

10/25missing: Mail Server Configuration, IPv6 Support

Domain Reputation

35/50missing: Typosquatting Check

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 5 lookups

SURBL MultidomainURIBL MultidomainSpamCop204.79.197.200Barracuda204.79.197.200UCEPROTECT Level 1204.79.197.200

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.net" \ -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.net"

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

IPv6. Does bing.net work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.

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