Skip to content
https://chip.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
5 PASS 4 REVIEW
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.chip.de/
200https://chip.de/

HTTP → HTTPS

403http://chip.de/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
2 A records, 32 ms lookup
PASS
2 A records, 32 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 2.17.112.39, 2.17.112.23
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:2380:d::211:7056, 2a02:26f0:2380:d::211:7045
Info::
6 nameserver(s) configured
Got: a28-65.akam.net, a16-67.akam.net, a1-118.akam.net, a5-66.akam.net, a2-64.akam.net, a7-67.akam.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: 32 ms
Got: 32 ms
A2.17.112.39, 2.17.112.23
AAAA2a02:26f0:2380:d::211:7056, 2a02:26f0:2380:d::211:7045
CNAME
NSa28-65.akam.net, a16-67.akam.net, a1-118.akam.net, a5-66.akam.net, a2-64.akam.net, a7-67.akam.net
MX
10 chip-de.mail.protection.outlook.com
TXT
SPF v=spf1 mx include:_spf.general.transactional-mail-a.com include:spf.protection.o...
adobe-idp-site-verification=3dd87aeb46d139cf0d8b7c78e2f0a96b5ebd3ad07d8aef6921d9...
atlassian-domain-verification=ADXdiaemzjJXv0Cxw8MbdL09b6EY1y3t3z4LrFR0l20l2wrMZe...
MS=ms18971433
CAALookup not available with standard resolver
Resolved in 32 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
0 redirect(s), 16 ms total
PASS
0 redirect(s), 16 ms total

https://chip.de

16 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://chip.de40316 msHTTP/1.1AkamaiGHost
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:2380:d::211:7056, 2a02:26f0:2380:d::211:7045
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:2380:d::211:7056, 2a02:26f0:2380:d::211:7045 Connection Reachable (1 ms)
A+
Domain Intelligence
chip.de
PASS
chip.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

202 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:2380:d::211:7045

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 2a02:26f0:2380:d::211:7045
Data source: whois (0.6s)

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.
44 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
58 ms
Total Time Total request time from DNS lookup through full response.
58 ms

Connection waterfall

DNS Lookup 44 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 9 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