Projects using managed instances can now add domains in bulk from a CSV file, instead of one at a time. The managed domains screen also gained filters and a DNS instructions export.

Importing domains from a CSV file

The Import domains button opens a wizard in four steps: choose a CSV file, confirm which column holds the domain names, choose the domains to import, and review the summary.

The third step is where the work happens. Before importing anything, redirection.io checks every domain in the file: whether it resolves in DNS, and what it currently answers over HTTP. Each row shows the status code the domain serves today, whether it redirects and to where, or whether it could not be reached at all.

That check is what makes a large import safe : a list of a few hundred domains, collected over the years in a spreadsheet, usually contains expired domains and entries already pointing somewhere else. Seeing that before the import avoids adding domains that will never serve traffic, and spending your managed instances quota on them.

The analysis runs in the background, which means you can close the panel and come back to it later: reopening it picks the analysis up where it was.

The CSV file only needs one column containing the domain names. If it has a header row with a recognizable name (domain, hostname, host or name), the column is detected automatically.

Filters and DNS instructions

The managed domains list now has a search field on the domain name, and a "display only domains with errors" toggle, which makes a long list easily workable.

The Export DNS instructions button downloads the DNS records to create for the domains currently listed. Filters are taken into account, so you can export only the subset you are working on and hand it over to whoever manages the DNS zone.

How to use it

Open your project, go to Instances, then to the managed domains tab. Bulk import is available on paid plans. Managing the domains of a managed instance is described in the instances documentation.

We have made a series of improvements to the traffic logs interface, focused on log details and filtering.

Richer log details

The detail view of a log entry now shows the details of the rule that was triggered for that request, so you can see exactly which rule matched, and which trigger and actions it applied, without leaving the log.

The request URL can also be broken down into its components: switch the URL field to "parsed" mode to see the scheme, host, path and query parameters listed separately, which makes long or parameter-heavy URLs much easier to read.

Clearer filtering

The log filters are now grouped into logical families - "Request", "Response" and "Other" - so the filter you need is easier to find. The same filters interface has also been carried over to the rules list, so filtering rules works just like filtering logs.

Together, the triggered-rule details, the parsed URL view and the reorganized filters make the redirection.io log explorer a genuinely comfortable tool to explore your traffic, and we have many more improvements in mind.

Open your traffic logs to try these out. Working with logs is described in the logs documentation.

We are migrating the load balancers of our managed instances to a new IPv6 addressing scheme.

• Old IPv6 address, retired on December 1st, 2026: 2001:41d0:301:100:51:91:60:76
• New IPv6 address: 2001:41d0:ac00:24c::1

IPv4 is not affected. Domains pointing to our managed instances with a CNAME record require no change: this only concerns AAAA records.

If one of your domains still resolves to the old IPv6 address, update the AAAA record in your DNS zone with the new value. Propagation depends on the TTL of your zone and can take up to 24 hours.

Both addresses answer traffic until December 1st, 2026, so there is no service interruption today. From November 1st, 2026, the manager displays a warning for domains still using the old address. After December 1st, the old address stops answering: visitors whose network prefers IPv6 would no longer reach your site over IPv6, and automatic SSL certificate renewals could fail.

Customers with an affected domain have been notified by email. If you have a doubt about your configuration, or if someone else manages your DNS zone, contact us and we will help.

The Convert HTML to Markdown action converts an HTML response to Markdown on the fly, directly at the edge. It comes with a redesigned action selector and support in the public API.

Markdown is a lightweight, plain-text formatting syntax: headings, links, lists and emphasis are written with a few simple characters instead of HTML tags. It is easy to read for humans and easy to parse for machines, which is why AI crawlers and LLM tools increasingly prefer it over full HTML pages.

A common use case is therefore to serve a Markdown version of your pages to those tools, without changing anything on your backend. The simplest way is through content negotiation: when a client requests a page with the Accept: text/markdown header, redirection.io returns the Markdown version.

curl -H "Accept: text/markdown" https://your-site.example/blog/some-page

Our new Convert HTML to Markdown recipe installs exactly this setup for a folder of your choice (or the whole site): it adds a Vary: Accept header on the matched URLs, and returns Markdown with a text/markdown content type when the client asks for it.

The recipe is the fastest way to get started: pick a folder, install it, and publish. You can then open the generated rules to fine-tune the trigger or add more actions.

You can also add the action manually to any rule. See the actions reference for details.

Many redirection.io users were not familiar with our notifications. To receive them, you first had to create a notification channel, then configure which events should be sent to it. We have made this much simpler.

An email channel, ready out of the box

Every new project now gets an email notification channel created automatically. Setting up notifications - for traffic anomalies, rule publications, or the lifecycle of your managed instances - is then just a matter of choosing which events to send. For existing projects, you can create a notification channel by hand at any time.

Choose exactly who gets notified

The email channel has also been reworked. Instead of a single recipient, you can now configure a list of addresses, with independent switches to notify all members of the project, all administrators of the project, and/or the author of the action that triggered the notification.

Every notification email includes a direct link to manage notification preferences, so recipients can adjust what they receive without leaving their inbox.

Open your project notifications settings to review the default channel and adjust its recipients.

We have shipped a batch of improvements to the redirection.io crawler, covering content quality checks, redirect diagnostics, more control over how a crawl runs, and a new way to follow how a site evolves over time.

New content and SEO checks

The crawl report includes several new signals:

1. Duplicate content detection: the crawler now flags pages whose content is strictly identical or nearly identical, using a simhash fingerprint. Duplicate content is a common SEO problem that used to be hard to spot across a large site.
2. Word count distribution: a new report section shows how word count is spread across all crawled pages, which helps locate thin pages with little content.
3. Redirect loops and redirects to an error: dedicated metrics and lists surface pages caught in a redirect loop, or that redirect to a page returning an error. Both are frequent SEO issues that were previously difficult to isolate.
4. Sitemap and well-known files: the report now warns when a sitemap exceeds the recommended size, or when standard URLs such as /.well-known/security.txt are missing.

More control over a crawl

You now have finer control over how the crawler behaves:

• Ignore robots directives: a crawl can be configured to deliberately ignore robots.txt rules, as well as noindex and nofollow directives in the HTML. This is useful to crawl a staging site or to run a full SEO audit.
• Custom HTTP headers: a crawl can send custom HTTP headers, for example to reach a staging environment protected by authentication.
• Delay between requests: you can set a delay between each request, including on recurring scheduled crawls, to avoid overloading a site.
• Automatic retry on HTTP error: the crawler now retries a failed request instead of giving up immediately, for more reliable reports on unstable sites.

With these additions, the redirection.io crawler is more configurable than ever, so it can reliably explore even sites that sit behind a web application firewall (WAF).

Follow a site's evolution

The former "Trends" tab has been replaced by a richer Evolution tab, which shows how a project's score and page states change from one crawl to the next, alongside a crawl performance chart. The crawl score is also displayed directly in the crawl list, so you can read it without opening each crawl.

The Evolution tab compares at least two crawls of the same project. Schedule recurring crawls to build up history automatically, and watch trends emerge over time.

To try these out, open the crawler from your project and start or schedule a crawl. Crawl configuration options are documented in the crawler documentation.

A brand new web analytics dashboard is now publicly available within the redirection.io platform. This feature is available in all plans, at no additional costs, and provides full analytics observability and traffic insights directly from the server level, eliminating the need for client-side tracking scripts.

For users of Matomo, Plausible, or traditional web analytics, redirection.io analytics serves as a functional replacement that eliminates frontend tracking overhead. It processes high-traffic volumes natively at the server level at no additional cost even in high volume contexts.

Core features and capabilities

The analytics interface delivers comprehensive tools to analyze website traffic behavior and infrastructure health:

1. Core traffic dashboard: Monitor live visitor metrics, track unexpected traffic spikes, and compare active traffic with historical data periods.
2. Technical traffic breakdown: Group incoming requests by referrers, device types, operating systems, browsers, and exact HTTP status codes to quickly isolate delivery errors.
3. Content and campaign optimization: Identify top-performing landing pages and monitor marketing campaign tracking parameters without modifying website code.
4. Advanced bot behavior diagnostics: Differentiate human visitors from search engine crawlers, scrapers, and automated tools in real time to optimize crawl budgets and mitigate malicious automated traffic.

The server-side advantage

Traditional tag-based analytics systems depend on JavaScript, which can degrade frontend performance and be blocked by browser extensions. Server-side analytics derivation offers distinct operational benefits:

• No JavaScript required: Track traffic accurately even when visitors have JavaScript disabled or utilize ad-blockers.
• Privacy compliant by design: Measure user engagement and traffic patterns without relying on invasive tracking cookies or harvesting personal identifiers.
• Real-time data availability: Access immediate data on server performance, protocols, and HTTP response states without session processing delays.

Implementation & how to install

redirection.io analytics are available right now within the redirection.io manager console. Since these analytics are directly derived from traffic logs, there is nothing more to install if redirection.io is already functional on your site!

We are thrilled to announce the official release of the redirection.io agent version 3. It took our team more than one year of intense work, including rigorous development tasks and extensive QA testing, to complete this milestone release. The v3 agent brings massive upgrades to our reverse proxy capabilities, observability, and overall scalability.

Massive upgrades to the reverse proxy

The overall features of the agent did not change: it remains a reliable piece of software, designed for resilience, performance, robustness, and security. The agent still supports the "server" mode, allowing it to run as a companion to the nginx and Apache native modules. However, the reverse proxy mode gained a lot of new features.

The v3 agent now acts as a highly performant reverse proxy supporting modern protocols, including HTTP/1, HTTP/2, and HTTP/3 (QUIC). It features built-in automated SSL/TLS certificate management using the ACME protocol (such as Let's Encrypt), which can be used alongside traditional local file certificates. Connections to your backend servers have been optimized with full IPv6 upstream forwarding support and persistent keep-alive connections.

We have also added built-in MaxMind GeoIP database support, allowing the agent to automatically inject location-based headers (such as country and city) into requests without relying on external CDNs. Additionally, the agent can now compress backend responses on the fly using gzip or brotli. For environments requiring distributed storage, the agent can now persist data, such as rules and SSL certificates, directly to an AWS S3 bucket instead of a local disk.

Enhanced observability and virtualhosts

To simplify infrastructure management, we introduced the concept of Virtualhosts. This new feature allows you to host and route multiple websites, utilizing different redirection.io project keys, on a single agent instance without needing to bind each site to a specific port.

For advanced monitoring, the v3 agent exposes an optional Prometheus-compatible metrics endpoint for real-time tracking of agent health, traffic, and performance. Access logs are also highly configurable now; they can be output in JSON, text, or syslog formats, and can be customized granularly at the Virtualhost level.

Upgrading to v3 and what it means for you

To upgrade, users of APT or RPM repositories simply need to update their repository URLs to the stable/3 branch. Please note that if you use the nginx or Apache modules, they must be upgraded synchronously to the 3.x branch alongside the agent. Our upgrade guide will provide detailed instructions to ensure a smooth transition.

Note that the v3 configuration format is not compatible with the v2.10 agent, so a migration of your existing configuration files will be necessary. A complete configuration example is available in our documentation, and we are here to assist you with any questions you may have during the migration process.

If you are not ready to migrate immediately, there is no need to worry. The 2.10 release of the agent will continue to work for years, and we guarantee backward compatibility at the API level so there will be no disruption to your services. In fact, the 3.x branch stack is already fully deployed and powering our managed instances offer. As for our Cloudflare and Fastly worker integrations, the v3 updates have not been released yet, but they will be available in a few weeks.

Thank you for your continued trust. We invite you to dive into our updated documentation to explore all the new capabilities of the v3 agent!

We have added a new "duration" filter to the logs interface to help you track your website's performance.

While analyzing http traffic logs is essential for seo, it isn't enough: understanding how long these requests take is also crucial for a good user experience. this update allows you to isolate slow requests and pinpoint the exact origin of potential delays.

What’s changing

We now collect detailed timing information for every request on your site. This data is available via a new "duration" column and a dedicated filter. Duration tracking is available in the latest stable versions of the agent. Users of managed instances also benefit from more detailed duration measurements (distinguishing between redirection.io and backend processing times), which will also be available in future versions of the agent.

Using duration data in logs

Navigate to your traffic logs page. You can add a "duration" column to the logs list to see the total processing time for each request (in milliseconds).

If your site uses redirection.io managed instances or version 3 of the agent (currently in beta), you can also view a precise breakdown of these timings. Hovering over the "duration" column displays a tooltip with two distinct metrics:

• redirection.io duration: the time required to analyze the request and find a matching rule.
• backend duration: the response time of your own server.

This distinction makes it easy to see instantly whether latency stems from a redirection rule or from your backend application.

When requests are grouped, the aggregated view also displays the average request duration for the group, as well as the duration under which 95% of the requests in the group were processed ("p95" or "95th percentile").

You will also find a new "duration" filter in the sidebar, allowing you to quickly identify requests that exceed a specific threshold (e.g., 2000 ms). This makes it possible to focus optimization efforts on the slowest parts of your site.

We are pleased to announce two new security recipes to enhance the protection of your web applications.

redirection.io recipes are predefined sets of rules that allow you to quickly configure behaviors and optimizations for your website: redirects, security, SEO, etc.

The new recipes we have added allow you to restrict access to certain parts of your website based on the visitor's IP address, and to block suspicious requests that might attempt to access sensitive data.

Restrict access by IP address

This recipe allows you to define rules to allow or block access to certain pages or sections of your website based on the visitor's IP address. For example, you can only allow your company's IP addresses to access an employee-only section.

This recipe can also be useful if you want to limit access to an admin interface or a test / pre-production version of your website.

Most importantly, like all redirection.io recipes, it can be modified to adapt to your specific needs. For example, you can modify this recipe to perform a redirect if the visitor's IP address is not authorized, instead of simply blocking access.

Discover how to restrict by IP address

Block malicious URLs

Even if you have implemented security measures to protect your website's sensitive data, it is still possible for attackers to try to access this data using malicious requests. In reality, across all websites whose traffic redirection.io analyzes, we observe that a significant portion of requests processed by web platforms are malicious, often automated requests, attempting to exploit known vulnerabilities.

This recipe allows you to automatically block requests that attempt to access sensitive files or directories, such as configuration files, databases, or administration scripts. You can also customize this recipe to block specific types of requests, depending on your website's needs.

Our estimates suggest that approximately 9 to 11% of requests processed by websites equipped with redirection.io are requests that could be blocked by this recipe, which can significantly reduce the load on your server, improve your website's security, prevent data leaks, and reduce your hosting costs.

Block suspicious requests or sensitive files access