Skip to content
https://www.prezi.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
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.prezi.com/
200https://prezi.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.prezi.com/ https://www.prezi.com/

Consistent

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

Certificate validity

165
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
2 A records, 48 ms lookup
PASS
2 A records, 48 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 99.83.220.209, 75.2.83.248
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 48 ms
Got: 48 ms
A99.83.220.209, 75.2.83.248
AAAA
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 48 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 924 ms total
PASS
1 redirect(s), 924 ms total
Info::
Single redirect
Got: https://www.prezi.com → https://prezi.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 924 ms total
Got: 924 ms

https://www.prezi.com

421 ms · HTTP/1.1

301

https://prezi.com/

503 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.prezi.com301421 msHTTP/1.1
2https://prezi.com/200503 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 7685 URLs
PASS
robots.txt present, sitemap with 7685 URLs
Info::
robots.txt is present
Got: 732 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7685 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 732 B Sitemaps referenced 6 User-agents *, ClaudeBot, GPTBot, Claude-SearchBot, OAI-SearchBot Blocking No — crawling allowed
User-agent: *
Disallow: /cms/
Disallow: /explore/search/
Disallow: /invoice/download/
Disallow: /login/

# Anthropic - AI training crawler (block)
User-agent: ClaudeBot
Disallow: /

# OpenAI - AI training crawler (block)
User-agent: GPTBot
Disallow: /

# Anthropic - AI search crawler (allow)
User-agent: Claude-SearchBot
Allow: /

# OpenAI - AI search crawler (allow)
User-agent: OAI-SearchBot
Allow: /

Sitemap: https://prezi.com/sitemap_seo_landing.xml
Sitemap: https://prezi.com/sitemap_next-prezis_index.xml
Sitemap: https://prezi.com/sitemap_classic-prezis_index.xml
Sitemap: https://prezi.com/sitemap_videos_index.xml
Sitemap: https://prezi.com/sitemap_marketing_index.xml
Sitemap: https://prezi.com/sitemap_design_index.xml

A+
Domain Intelligence
prezi.com — via Amazon Registrar, Inc., 25 years, 11 months old, hosted on AWS
PASS
prezi.com — via Amazon Registrar, Inc., 25 years, 11 months old, hosted on AWS
Info::
Domain registered until Aug 24, 2026 (4 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: Amazon Registrar, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

42 days

August 24, 2026

SSL certificate

165 days

Issued by Amazon

Domain age

25 years, 11 months

Registered August 24, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.83.248

Registrar

Amazon Registrar, Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Amazon Registrar, Inc.
Created August 24, 2000 (25 years, 11 months ago)
Expires August 24, 2026 (4 months)
Last Updated July 20, 2025
Name Servers ns-1218.awsdns-24.org, ns-1914.awsdns-47.co.uk, ns-422.awsdns-52.com, ns-554.awsdns-05.net
DNSSEC Not enabled
Hosting
IP Address 75.2.83.248
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

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

Connection waterfall

DNS Lookup 38 ms TCP Connect 1 ms TLS Handshake 307 ms Server Processing 105 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