Infrastructure - https://www.bing.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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

DNS Records

2 A records, 33 ms lookup

REVIEW

2 A records, 33 ms lookup

Resolves to 2 IPv4 address(es)

Got: 95.100.86.226, 95.100.86.220

Has 2 IPv6 (AAAA) record(s)

Got: 2a02:26f0:2380:19::17d3:f48, 2a02:26f0:2380:19::17d3:f56

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: www-www.bing.com.trafficmanager.net

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 33 ms

Got: 33 ms

A	95.100.86.226, 95.100.86.220
AAAA	2a02:26f0:2380:19::17d3:f48, 2a02:26f0:2380:19::17d3:f56
CNAME	www-www.bing.com.trafficmanager.net
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 33 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B

Subdomain Takeover

CNAME points at managed service(s) — verify configuration

REVIEW

CNAME points at managed service(s) — verify configuration

CNAME targets Azure Traffic Manager — verify ownership

CNAME targets Azure Traffic Manager. Deleted profiles free the name. Confirm the Traffic Manager profile is still configured.

Got: www-www.bing.com.trafficmanager.net

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

B

Reverse DNS

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR for 95.100.86.226 does not match any cert SAN: a95-100-86-226.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 95.100.86.220 does not match any cert SAN: a95-100-86-220.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a02:26f0:2380:19::17d3:f48 does not match any cert SAN: g2a02-26f0-2380-0019-0000-0000-17d3-0f48.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a02:26f0:2380:19::17d3:f56 does not match any cert SAN: g2a02-26f0-2380-0019-0000-0000-17d3-0f56.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

B

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: www)

HTTP version does not redirect to HTTPS

Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.bing.com/

301https://bing.com/

Preferred variant: www

HTTP → HTTPS

200http://www.bing.com/

HTTP version does not redirect to HTTPS

B

TLS Certificate Expiry & Recommendations

83 days until leaf cert expires — 1 issues to address

REVIEW

Certificate validity

83

days left

0d 30d 60d 90d+

Recommended actions

Enable DNSSEC on your domain for DNS spoofing protection

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 410, /status: 404.

A+

Multi-Resolver DNS Speed

Mean 16ms across 3 resolvers (spread 32ms)

PASS

Mean 16ms across 3 resolvers (spread 32ms)

Quad9: 0ms

Got: 0ms via 9.9.9.9:53

Cloudflare: 16ms

Got: 16ms via 1.1.1.1:53

Google: 32ms

Got: 32ms via 8.8.8.8:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.bing.com

https://www.bing.com

71 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.bing.com	200	71 ms	HTTP/1.1

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2a02:26f0:2380:19::17d3:f48, 2a02:26f0:2380:19::17d3:f56

Got: 1 ms connect

IPv6 Ready

AAAA Records 2a02:26f0:2380:19::17d3:f48, 2a02:26f0:2380:19::17d3:f56 Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 12 URLs

PASS

robots.txt present, sitemap with 12 URLs

robots.txt is present

Got: 2676 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 12 entries

Sitemap index with 12 child sitemaps

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, 8 months old

PASS

bing.com — via MarkMonitor Inc., 30 years, 8 months old

Domain registered until Jan 30, 2027 (8 months remaining)

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.

Registrar: MarkMonitor Inc.

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

257 days

January 30, 2027

SSL certificate

83 days

Issued by Microsoft Corporation

Domain age

30 years, 8 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, 8 months ago)

Expires January 30, 2027 (8 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 138 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

40 ms

TCP Connect

1 ms

TLS Handshake

5 ms

Time to First Byte

113 ms

Total Time

139 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 67 ms Content Transfer 26 ms