Skip to content
https://bing.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
2
REVIEW
1
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
6 PASS 1 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.bing.com/
200https://bing.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://bing.com/ → http://www.bing.com/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
TLS Certificate Expiry & Recommendations
107 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

107
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 4 ms lookup
PASS
2 A records, 4 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 150.171.27.10, 150.171.28.10
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:1ec:33:1::10, 2620:1ec:33::10
Info::
8 nameserver(s) configured
Got: ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info, dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 4 ms
Got: 4 ms
A150.171.27.10, 150.171.28.10
AAAA2620:1ec:33:1::10, 2620:1ec:33::10
CNAME—
NSns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info, dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net
MX
10 bing-com.mail.protection.outlook.com
TXT
facebook-domain-verification=09yg8uzcfnqnlqekzsbwjxyy8rdck7
google-site-verification=OkRY8R261shK5B8uEwvsFZp9nQ2gRoHavGlruok1azc
google-site-verification=SHuSHN0Hv3nwBI9So329KwfbQ7xLif64SRwcGSdWNAU
v=msv1 t=6097A7EA-53F7-4028-BA76-6869CB284C54
SPF v=spf1 include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 4 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 114 ms total
PASS
1 redirect(s), 114 ms total
Info::
Single redirect
Got: https://bing.com → https://www.bing.com:443/?toWww=1&redig=3B662F22894E418D9DEC31E02B1FC027 (301)
Info::
WWW normalization redirect

https://bing.com

47 ms · HTTP/1.1

301

https://www.bing.com:443/?toWww=1&redig=...

67 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bing.com30147 msHTTP/1.1
2https://www.bing.com:443/?toWww=1&redig=...20067 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2620:1ec:33:1::10, 2620:1ec:33::10
Got: 2 ms connect
IPv6 Ready
AAAA Records 2620:1ec:33:1::10, 2620:1ec:33::10 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 2676 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2676 B Sitemaps referenced 1 User-agents msnbot-media, Twitterbot, * Blocking No — crawling allowed
User-agent: msnbot-media

Disallow: /

Allow: /th?


User-agent: Twitterbot

Disallow:


User-agent: *

Disallow: /academic/profile

Disallow: /academic/search

Disallow: /account/

Disallow: /aclick

Disallow: /alink

Disallow: /amp/

Allow: /api/maps/

Disallow: /api/

Disallow: /bfp/search

Disallow: /bing-site-safety

Disallow: /blogs/search/

Disallow: /ck/

Disallow: /copilotsearch?q=

Disallow: /cr$

Disallow: /cr?

Disallow: /entities/search

Disallow: /entityexplore$

Disallow: /entityexplore?

Disallow: /fd/

Disallow: /fun/api/

Disallow: /fun/g/

Disallow: /history

Disallow: /hotel/reviews?

Disallow: /hotels/search

Disallow: /HpImageArchive.aspx

Disallow: /hpm

Disallow: /hpmob

Disallow: /images/async/?

Disallow: /images/async?

Disallow: /images/hosted/?

Disallow: /images/hosted/search?

Disallow: /images/hosted?

Disallow: /images/search%3F

Disallow: /images/search%5C

Disallow: /images/search/?

Disallow: /images/search?

Disallow: /images/searchbyimage

Disallow: /images?

Disallow: /inboxcommerce

Disallow: /local

Disallow: /maps/adsendpoint

Disallow: /merchant/reviews?

Disallow: /notifications/

Disallow: /offers/proxy/dealsserver/api/log

Disallow: /offers/proxy/dealsserver/buy

Disallow: /ping

Disallow: /product/reviews?

Disallow: /profile/history?

Disallow: /proFile/history?

Disallow: /Proxy.ashx

Disallow: /results

Disallow: /rewardsapp/

Disallow: /search

Disallow: /Search

Disallow: /settings

Disallow: /shenghuo

Allow: /shop$

Allow: /shop/

Disallow: /shop/collections

Disallow: /shop/productpage

Disallow: /shop/topics

Disallow: /shop?*

Disallow: /social/search?

Disallow: /spbasic

Disallow: /spresults

Disallow: /static/

Disallow: /th$

Disallow: /th?

Disallow: /translator/?ref=

Disallow: /travel/api

Disallow: /travel/css

Disallow: /travel/flight/flightSearch

Disallow: /travel/flight/flightSearchAction

Disallow: /travel/flight/search/?

Disallow: /travel/flight/search?

Disallow: /travel/flights

Disallow: /travel/flight-search

Disallow: /travel/hotel/hotelMiniSearchRequest

Disallow: /travel/hotel/hotelSearch

Disallow: /travel/hotels/checkout

Disallow: /travel/hotels/detail

Disallow: /travel/hotels/search/?

Disallow: /travel/hotels/search?

Disallow: /travel/hotel-search

Disallow: /travel/scripts

Disallow: /travel/secure

Disallow: /url

Disallow: /videos/browsing

Disallow: /videos/explore

Disallow: /videos/favorites

Disallow: /videos/feed

Disallow: /videos/music

Disallow: /videos/trending

Disallow: /widget/cr

Disallow: /widget/entity/search/?

Disallow: /widget/render

Disallow: /widget/snapshot

Disallow: /work


Sitemap: https://www.bing.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 12 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
bing.com — via MarkMonitor Inc., 30 years, 7 months old
PASS
bing.com — via MarkMonitor Inc., 30 years, 7 months old
Info::
Domain registered until Jan 30, 2027 (9 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

202 days

January 30, 2027

SSL certificate

107 days

Issued by Microsoft Corporation

Domain age

30 years, 7 months

Registered January 29, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:1ec:33:1::10

Registrar

MarkMonitor Inc.

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created January 29, 1996 (30 years, 7 months ago)
Expires January 30, 2027 (9 months)
Last Updated December 29, 2025
Name Servers dns1.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
DNSSEC Not enabled
Hosting
IP Address 2620:1ec:33:1::10
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 58 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
2 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
59 ms
Total Time Total request time from DNS lookup through full response.
59 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 1 ms TLS Handshake 24 ms Server Processing 32 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback