Skip to content
https://ted.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 3 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.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ted.com/ → https://ted.com/

Consistent

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

Certificate validity

107
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
  • 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, 26 ms lookup
PASS
2 A records, 26 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 34.198.81.154, 3.211.142.64
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1133.awsdns-13.org, ns-191.awsdns-23.com, ns-1975.awsdns-54.co.uk, ns-882.awsdns-46.net
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: 26 ms
Got: 26 ms
A34.198.81.154, 3.211.142.64
AAAA—
CNAME—
NSns-1133.awsdns-13.org, ns-191.awsdns-23.com, ns-1975.awsdns-54.co.uk, ns-882.awsdns-46.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
TXT
atlassian-domain-verification=4timsOUsdaVIPDVxoNaau9lRel9P83lqXmmmtsIImOt3GfoVq5...
canva-site-verification=o-gjQy5XSCZFLMlzw9BblQ
google-site-verification=UIn4zpG4F9qybIzoM2BeT-O2H3RG6M4vgoC_n8CPzW0
mandrill_verify.iMtYQCwMRNE7tcpyMxeGwQ
tollbit-domain-verification=87fdc3e9954c4a72ae699c04473015754a5d64bfa5002a5cb470...
SPF v=spf1 include:aspmx.sailthru.com include:spf.mandrillapp.com include:_spf.googl...
CAALookup not available with standard resolver
Resolved in 26 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), 427 ms total
PASS
1 redirect(s), 427 ms total
Info::
Single redirect
Got: https://ted.com → https://www.ted.com/ (301)
Info::
WWW normalization redirect

https://ted.com

404 ms · HTTP/1.1

301

https://www.ted.com/

23 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ted.com301404 msHTTP/1.1nginx
2https://www.ted.com/20023 msHTTP/1.1nginx/1.27.5

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 29 URLs
PASS
robots.txt present, sitemap with 29 URLs
Info::
robots.txt is present
Got: 1040 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 29 entries
Info::
Sitemap index with 29 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1040 B Sitemaps referenced 1 User-agents Meta-ExternalAgent, OAI-SearchBot, Amazonbot, anthropic-ai, Applebot-Extended, Diffbot, PerplexityBot, *, ChatGPT-User, FacebookBot, omgili, GPTBot, Baiduspider, Bytespider, ClaudeBot, cohere-ai, ImagesiftBot, meta-externalagent, omgilibot, CCBot, FriendlyCrawler Blocking No — crawling allowed
User-agent: *
Disallow: /search
Disallow: /latest
Disallow: /latest-talk
Disallow: /latest-playlist
Disallow: /people
Disallow: /profiles
Disallow: /themes/rss

User-agent: Baiduspider
Disallow: /search
Disallow: /latest
Disallow: /latest-talk
Disallow: /latest-playlist
Disallow: /people
Disallow: /profiles

User-agent: Amazonbot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: FriendlyCrawler
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: meta-externalagent
User-agent: Meta-ExternalAgent
Disallow: /

User-Agent: OAI-SearchBot
Allow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-Agent: PerplexityBot
Disallow: /

Sitemap: https://www.ted.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 29 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ted.com — via Name.com, Inc., 31 years, 10 months old, hosted on AWS
PASS
ted.com — via Name.com, Inc., 31 years, 10 months old, hosted on AWS
Info::
Domain registered until Nov 7, 2026 (6 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: Name.com, Inc.
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: AS14618
Domain expiry

146 days

November 7, 2026

SSL certificate

107 days

Issued by Amazon

Domain age

31 years, 10 months

Registered November 8, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.198.81.154

Registrar

Name.com, Inc.

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 Name.com, Inc.
Created November 8, 1994 (31 years, 10 months ago)
Expires November 7, 2026 (6 months)
Last Updated October 8, 2025
Name Servers ns-1133.awsdns-13.org, ns-191.awsdns-23.com, ns-1975.awsdns-54.co.uk, ns-882.awsdns-46.net
DNSSEC Not enabled
Hosting
IP Address 34.198.81.154
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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 401 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
93 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
190 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
401 ms
Total Time Total request time from DNS lookup through full response.
402 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 93 ms TLS Handshake 190 ms Server Processing 96 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