Skip to content
https://infoq.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
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
Redirect Chain
1 redirect(s), 1535 ms total
REVIEW
1 redirect(s), 1535 ms total
Info::
Single redirect
Got: https://infoq.com → https://www.infoq.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1535 ms total
Got: 1535 ms

https://infoq.com

696 ms · HTTP/1.1

301

https://www.infoq.com/

839 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://infoq.com301696 msHTTP/1.1Apache
2https://www.infoq.com/200839 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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.infoq.com/
200https://infoq.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://infoq.com/ → https://infoq.com:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
3 A records, 36 ms lookup
PASS
3 A records, 36 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 100.22.79.172, 35.155.58.140, 52.36.194.255
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-514.awsdns-00.net, ns-1969.awsdns-54.co.uk, ns-1373.awsdns-43.org, ns-160.awsdns-20.com
Info::
6 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: 36 ms
Got: 36 ms
A100.22.79.172, 35.155.58.140, 52.36.194.255
AAAA—
CNAME—
NSns-514.awsdns-00.net, ns-1969.awsdns-54.co.uk, ns-1373.awsdns-43.org, ns-160.awsdns-20.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx4.googlemail.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
brevo-code:ddff45e0e8ae620f2868965a08245863
SPF v=spf1 mx include:_spf.google.com include:amazonses.com ~all
CAALookup not available with standard resolver
Resolved in 36 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+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 2553 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 2553 B Sitemaps referenced 1 User-agents *, rogerbot, Baiduspider, Sogou Spider, Sogou*, ScoutJet, dotbot, trendkite-akashic-crawler Blocking No — crawling allowed
Sitemap: https://www.infoq.com/sitemap.xml

User-agent: *
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 3

User-agent: rogerbot
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /CN1
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 10

User-agent: Baiduspider
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /CN1
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 10

User-Agent: Sogou Spider
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /CN1
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 10

User-Agent: Sogou*
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /CN1
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 10

User-agent: ScoutJet
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /CN1
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 20

User-agent: dotbot
Disallow: /metrics/ajaxMetricsLogAction.action
Disallow: /CN1
Disallow: /fr/Flash
Disallow: /br/Decorators
Disallow: /jp/Flash
Disallow: /social/
Disallow: /fr/social/
Disallow: /br/social/
Disallow: /cn/social/
Disallow: /jp/social/
Disallow: /cn/
Disallow: /url/
Disallow: /vendorcontent/
Disallow: /scripts/
Crawl-delay: 20

User-agent: dotbot
Crawl-delay: 20

User-agent: trendkite-akashic-crawler
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 12 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
infoq.com — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 30 years, 6 months old, hosted on AWS
PASS
infoq.com — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 30 years, 6 months old, hosted on AWS
Info::
Domain registered until Mar 30, 2027 (11 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: CSL Computer Service Langenbach GmbH d/b/a joker.com
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

254 days

March 30, 2027

SSL certificate

190 days

Issued by Amazon

Domain age

30 years, 6 months

Registered March 29, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

100.22.79.172

Registrar

CSL Computer Service Langenbach GmbH d/b/a joker.com

Unlocked 4 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 CSL Computer Service Langenbach GmbH d/b/a joker.com
Created March 29, 1996 (30 years, 6 months ago)
Expires March 30, 2027 (11 months)
Last Updated February 28, 2026
Name Servers ns-1373.awsdns-43.org, ns-160.awsdns-20.com, ns-1969.awsdns-54.co.uk, ns-514.awsdns-00.net
DNSSEC Not enabled
Hosting
IP Address 100.22.79.172
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 737 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.
172 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
346 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
738 ms
Total Time Total request time from DNS lookup through full response.
738 ms

Connection waterfall

DNS Lookup 44 ms TCP Connect 172 ms TLS Handshake 346 ms Server Processing 175 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