Skip to content
https://speakerdeck.com

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
200 OK
Checks
9
7 PASS 2 REVIEW
B
Domain Intelligence
speakerdeck.com — via 1API GmbH, 16 years, 2 months old
REVIEW
speakerdeck.com — via 1API GmbH, 16 years, 2 months old
Critical::
Domain expires in 21 days
This domain expires on May 12, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 12, 2026
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: 1API GmbH
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

EXPIRED

May 12, 2026

SSL certificate

43 days

Issued by Google Trust Services

Domain age

16 years, 2 months

Registered May 12, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::6814:1cb5

Registrar

1API GmbH

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 1API GmbH
Created May 12, 2010 (16 years, 2 months ago)
Expires May 12, 2026 (21 days)
Last Updated November 22, 2025
Name Servers john.ns.cloudflare.com, nola.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::6814:1cb5
Data source: rdap (0.4s)

This domain expires on May 12, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 14 ms lookup
PASS
2 A records, 14 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.158.156, 104.20.28.181
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::ac42:9e9c, 2606:4700:10::6814:1cb5
Info::
2 nameserver(s) configured
Got: john.ns.cloudflare.com, nola.ns.cloudflare.com
Info::
5 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: 14 ms
Got: 14 ms
A172.66.158.156, 104.20.28.181
AAAA2606:4700:10::ac42:9e9c, 2606:4700:10::6814:1cb5
CNAME
NSjohn.ns.cloudflare.com, nola.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
ALIAS for speakerdeck.com.herokudns.com
facebook-domain-verification=5rzw9hjdxxzobpi4p6lk9tlvpldfej
google-site-verification=3ggCXuHu3Wkywh0QJ4MVBy9jz0MMfAEVJGNVQP56eyY
google-site-verification=U0zznvYUS5x_csx7-HqM5TJh-EGrTvjQOR7wCPGyv74
stripe-verification=51e5bf1257eaab3496a4c15cdce19f2c27d591dd7d87097e936b1fbc2e84...
SPF v=spf1 include:mailgun.org ~all
CAALookup not available with standard resolver
Resolved in 14 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://speakerdeck.com

https://speakerdeck.com

447 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://speakerdeck.com200447 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::ac42:9e9c, 2606:4700:10::6814:1cb5
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::ac42:9e9c, 2606:4700:10::6814:1cb5 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 22 URLs
PASS
robots.txt present, sitemap with 22 URLs
Info::
robots.txt is present
Got: 647 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 22 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 647 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /*signin?*
Disallow: /*kolkata*
Disallow: /*call-0821*
Disallow: /*return_to=*
Disallow: /*share.php?*
Disallow: /*.atom*
Allow: /p/all.atom?page=10
Allow: /p/all.atom?page=9
Allow: /p/all.atom?page=8
Allow: /p/all.atom?page=7
Allow: /p/all.atom?page=6
Allow: /p/all.atom?page=5
Allow: /p/all.atom?page=4
Allow: /p/all.atom?page=3
Allow: /p/all.atom?page=2
Allow: /p/all.atom?page=1
Allow: /p/all.atom
Allow: /c/how-to-diy.atom
Allow: /c/technology.atom
Allow: /c/science.atom
Allow: /c/research.atom
Allow: /c/programming.atom
Allow: /c/design.atom
Allow: /c/business.atom
Allow: /p/featured.atom
Allow: /c/education.atom

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.speakerdeck.com/
200https://speakerdeck.com/

Preferred variant: non-www

HTTP → HTTPS

301http://speakerdeck.com/ https://speakerdeck.com/

Consistent

A
HTTP Probe Timing
Total 494 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.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
433 ms
Total Time Total request time from DNS lookup through full response.
494 ms

Connection waterfall

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

Send Feedback