redirect.pizza

@redirect.pizza list all my active redirects and show which ones have SSL certificates ready

Found 12 active redirects across your team. 9 have verified SSL certificates: your marketing short-links (go.acme.co → landing pages), the support redirect (help.acme.co → Zendesk), and 6 campaign URLs. 3 redirects are pending DNS verification: promo.acme.co, event.acme.co, and demo.acme.co — these won't serve HTTPS traffic until you update your DNS records to point to redirect.pizza's nameservers. All verified domains show green SSL status with auto-renewal enabled.

This example shows the MCP's domain-listing and SSL-state tools working together. Requires an API key with read access to your redirect.pizza team. The MCP can surface DNS and SSL issues before users encounter broken links, but it won't auto-fix DNS — you still configure records in your registrar.

@redirect.pizza create a redirect from launch.acme.co to https://acme.co/products/new-feature and generate a QR code for it

Created redirect ID rdr_8x3k with source launch.acme.co pointing to https://acme.co/products/new-feature. DNS records required: CNAME launch.acme.co → redirect.pizza's edge. SSL will provision automatically once DNS propagates (usually 5–15 minutes). Generated a 512px PNG QR code embedding https://launch.acme.co — you can drop this in print materials or slide decks. The redirect is live but will return a DNS error until you update your registrar.

Demonstrates create-redirect and generate-QR-code tools in one workflow. The MCP returns the redirect ID and QR image data, but you must manually configure DNS before the redirect works. If your team is on a free plan, only certain redirect types (301, 302) are available — the MCP will error on advanced types like cloaked or A/B split redirects.

@redirect.pizza check DNS propagation for event.acme.co and tell me if it's safe to share the link publicly

Ran a fresh DNS check for event.acme.co. Current state: CNAME correctly points to redirect.pizza's edge (verified from 4 global resolvers), SSL certificate issued 3 hours ago and valid for 90 days. The domain is fully propagated and serving HTTPS with no mixed-content warnings. Safe to share publicly — the redirect to https://acme.co/events/summit-2025 is live and will handle traffic without errors. Note: redirect.pizza's free tier allows 1,000 hits/month per domain; if you expect high traffic, consider upgrading to avoid rate-limit pauses.

This example pairs the check-domain-DNS tool with the AI's synthesis to answer a go/no-go question. Useful before launching a campaign. The MCP returns raw DNS and SSL state; the AI interprets whether it's production-ready. Be aware that DNS propagation is eventually consistent — a 'verified' status doesn't guarantee every global resolver sees it instantly.

When redirect.pizza beats spreadsheet link management

A 3-person growth team running paid ads across Meta, Google, and LinkedIn needs to swap landing pages mid-campaign without republishing creative. redirect.pizza wins here because you create one branded short link per channel, then update the destination URL through the API when you pivot from the webinar page to the case-study download. The QR code tool means your print collateral stays valid when the offer changes. This breaks down if you're running 50+ concurrent campaigns—at that scale you want a full marketing-ops platform with attribution and A/B testing baked in. But for teams under 10 campaigns a month who just need reliable, fast redirects they can script, redirect.pizza is the right weight.

Redirect management for product teams shipping weekly

A 6-person product team at a B2B SaaS company ships feature updates every sprint and needs onboarding emails to point at the current UI, not last quarter's deprecated flow. redirect.pizza's API lets you version your help links in the codebase: when you merge the new dashboard, a deploy hook updates the redirect destination so existing emails route correctly. The DNS-check tool matters because you're using custom subdomains like go.yourapp.com and can't afford a 48-hour propagation mystery. This setup works until you need per-user personalization or complex conditional routing—then you're in marketing-automation territory. For straightforward destination updates tied to deploy cycles, redirect.pizza keeps your docs accurate without a CMS.

When QR generation belongs in your redirect stack

A 4-person events team running quarterly meetups needs printable QR codes for registration that redirect to the live event page, which changes from 'register' to 'join Zoom' to 'watch recording' over three weeks. redirect.pizza's QR-code tool outputs print-ready SVG and EPS, and the redirect API means one code works across all three phases—you just update the destination URL as the event progresses. The domain-verification flow lets you use meetup.yourcompany.com so the QR doesn't look like a phishing attempt. This stops being the right tool if you need per-attendee tracking or badge integration—that's Eventbrite's job. For small-scale events where you control the redirect logic and want one durable QR per event series, redirect.pizza is lighter than a full event platform.