Skip to content
https://businessinsider.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.businessinsider.de/
200https://businessinsider.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://businessinsider.de/ → https://businessinsider.de/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 6 ms lookup
PASS
2 A records, 6 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.173.21, 104.20.31.148
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:1f94, 2606:4700:10::ac42:ad15
Info::
2 nameserver(s) configured
Got: charles.ns.cloudflare.com, lola.ns.cloudflare.com
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: 6 ms
Got: 6 ms
A172.66.173.21, 104.20.31.148
AAAA2606:4700:10::6814:1f94, 2606:4700:10::ac42:ad15
CNAME—
NScharles.ns.cloudflare.com, lola.ns.cloudflare.com
MX
0 businessinsider-de.mail.protection.outlook.com
TXT
MS=ms61902796
facebook-domain-verification=msagaj7i0yjh3tgte9cy3qrvf91ifb
globalsign-domain-verification=MT3LmRzGYPgORWLlSBkPpAUpBDH9kl8xxYmB6FjtjY
google-site-verification=A32x37H5AhUcX0pXeELtPzdC33p2wFp9rSmh9gIuwHg
google-site-verification=HYG2-qCM72jzcwFeWBY5MZtZHM6T7CfZbWx5ZWsPRfE
google-site-verification=krDl8k0JsVguMYafvOukrZdrC4W2x9NHM3aaMg7HjK4
gveiil5m7ba9r0hddjh8sinlni
proxy-ssl.webflow.com
SPF v=spf1 include:spf.asv.de include:spf.protection.outlook.com include:amazonses.c...
CAALookup not available with standard resolver
Resolved in 6 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), 337 ms total
PASS
1 redirect(s), 337 ms total
Info::
Single redirect
Got: https://businessinsider.de → https://www.businessinsider.de/ (301)
Info::
WWW normalization redirect

https://businessinsider.de

167 ms · HTTP/1.1

301

https://www.businessinsider.de/

170 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://businessinsider.de301167 msHTTP/1.1cloudflare
2https://www.businessinsider.de/200170 msHTTP/1.1cloudflare

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 2606:4700:10::6814:1f94, 2606:4700:10::ac42:ad15
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:1f94, 2606:4700:10::ac42:ad15 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 140 URLs
PASS
robots.txt present, sitemap with 140 URLs
Info::
robots.txt is present
Got: 3176 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 140 entries
Info::
Sitemap index with 140 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3176 B Sitemaps referenced 3 User-agents Perplexity-User, PerplexityBot, SemrushBot-OCOB, SemrushBot-SWA, YandexAdditional, Facebot, aiHitBot, Bytespider, cohere-training-data-crawler, FirecrawlAgent, MyCentralAIScraperBot, Sidetrade indexer bot, LCC, bedrockbot, ClaudeBot, EchoboxBot, Google-CloudVertexBot, GoogleOther-Video, SBIntuitionsBot, Scrapy, Andibot, Claude-SearchBot, img2dataset, SemrushBot, sogou spider, TikTokSpider, meta-externalfetcher, Amazonbot, Datenbank Crawler, FacebookBot, magpie-crawler, Meta-ExternalFetcher, MistralAI-User, *, GPTBot, Applebot-Extended, CCBot, cohere-ai, ICC-Crawler, ImagesiftBot, NovaAct, AI2Bot, Devin, GoogleAgent-Mariner, GoogleOther-Image, QuillBot, SummalyBot, Timpibot, TurnitinBot, Baiduspider, Brightbot 1.0, Echobot Bot, MistralAI-User/1.0, netEstate Imprint Crawler, quillbot.com, WARDBot, Webzio-Extended, GoogleOther, Meta-ExternalAgent, Operator, panscient.com, PetalBot, YouBot, Ai2Bot-Dolma, Claude-User, FriendlyCrawler, Panscient, SemrushBot-SA, VelenPublicWebCrawler, BLEXBot, Cotoyogi, DataForSeoBot, Diffbot, Flamingo_SearchEngine, iaskspider/2.0, PhindBot, wpbot, Google-Extended, ISSCyberRiskCrawler, omgili, sentibot, TerraCotta, AhrefsBot, dotbot, omgilibot, PanguBot, Poseidon Research Crawler, anthropic-ai, Gemini-Deep-Research, SirdataBot, YandexAdditionalBot, Yeti, Awario, DuckAssistBot, Factset_spyderbot, MJ12bot, QualifiedBot, meta-externalagent, Crawlspace, ia_archiver, Kangaroo Bot, Thinkbot, Claude-Web Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Disallow: /cdn-cgi/

Allow: /wp-admin/admin-ajax.php


# Allow specific AI crawlers

User-agent: Facebot

User-agent: GPTBot

Allow: /


User-agent: AhrefsBot

User-agent: AI2Bot

User-agent: Ai2Bot-Dolma

User-agent: aiHitBot

User-agent: Amazonbot

User-agent: Andibot

User-agent: anthropic-ai

User-agent: Applebot-Extended

User-agent: Awario

User-agent: Baiduspider

User-agent: bedrockbot

User-agent: BLEXBot

User-agent: Brightbot 1.0

User-agent: Bytespider

User-agent: CCBot

User-agent: Claude-SearchBot

User-agent: Claude-User

User-agent: Claude-Web

User-agent: ClaudeBot

User-agent: cohere-ai

User-agent: cohere-training-data-crawler

User-agent: Cotoyogi

User-agent: Crawlspace

User-agent: DataForSeoBot

User-agent: Datenbank Crawler

User-agent: Devin

User-agent: Diffbot

User-agent: dotbot

User-agent: DuckAssistBot

User-agent: Echobot Bot

User-agent: EchoboxBot

User-agent: FacebookBot

User-agent: Factset_spyderbot

User-agent: FirecrawlAgent

User-agent: Flamingo_SearchEngine 

User-agent: FriendlyCrawler

User-agent: Gemini-Deep-Research

User-agent: Google-CloudVertexBot

User-agent: Google-Extended

User-agent: GoogleAgent-Mariner

User-agent: GoogleOther

User-agent: GoogleOther-Image

User-agent: GoogleOther-Video

User-agent: ia_archiver

User-agent: iaskspider/2.0

User-agent: ICC-Crawler

User-agent: ImagesiftBot

User-agent: img2dataset

User-agent: ISSCyberRiskCrawler

User-agent: Kangaroo Bot

User-agent: LCC

User-agent: magpie-crawler

User-agent: Meta-ExternalAgent

User-agent: Meta-ExternalFetcher

User-agent: MistralAI-User

User-agent: MistralAI-User/1.0

User-agent: MJ12bot

User-agent: MyCentralAIScraperBot

User-agent: netEstate Imprint Crawler

User-agent: NovaAct

User-agent: omgili

User-agent: omgilibot

User-agent: Operator

User-agent: PanguBot

User-agent: Panscient

User-agent: panscient.com

User-agent: Perplexity-User

User-agent: PerplexityBot

User-agent: PetalBot

User-agent: PhindBot

User-agent: Poseidon Research Crawler

User-agent: QualifiedBot

User-agent: QuillBot

User-agent: quillbot.com

User-agent: SBIntuitionsBot

User-agent: Scrapy

User-agent: SemrushBot

User-agent: SemrushBot-OCOB

User-agent: SemrushBot-SA

User-agent: SemrushBot-SWA

User-agent: sentibot

User-agent: Sidetrade indexer bot

User-agent: SirdataBot

User-agent: sogou spider

User-agent: SummalyBot

User-agent: TerraCotta

User-agent: Thinkbot

User-agent: TikTokSpider

User-agent: Timpibot

User-agent: TurnitinBot

User-agent: VelenPublicWebCrawler

User-agent: WARDBot

User-agent: Webzio-Extended

User-agent: wpbot

User-agent: YandexAdditional

User-agent: YandexAdditionalBot

User-agent: Yeti

User-agent: YouBot

Disallow: /


# Disallow specific AI crawlers

User-agent: meta-externalagent

User-agent: meta-externalfetcher

Disallow: /


# Sitemaps

Sitemap: https://www.businessinsider.de/news-sitemap.xml

Sitemap: https://www.businessinsider.de/sitemap_index.xml
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.businessinsider.de/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 140 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
businessinsider.de
PASS
businessinsider.de
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

Unknown

SSL certificate

60 days

Issued by Google Trust Services

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:ad15

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 2606:4700:10::ac42:ad15
Data source: whois (1.0s)

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 462 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 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.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
463 ms
Total Time Total request time from DNS lookup through full response.
463 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 445 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9f0886a31a151b1b-GRU
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f0886a31a151b1b-GRU
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback