Website profiles · Technology insights · Alternatives

anon.to

Shorten and redirect any URL anonymously. anon.to hides your referrer, doesn't track clicks, and keeps your browsing private. Free and open.

No paid content found
Visit website
Profile views 4 Outbound visits 0 Normal
anon.to Full homepage screenshot

At a glance

Category
Resources & Utilities
Language
English
Paid-content signal
No paid content foundObserved
Registered
2015
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is anon.to?

anon.to is an anonymous URL shortener and redirect service. It turns a long web address into a short anon.to link, or redirects a URL directly without creating a short link at all. According to the site itself, redirects run over HTTPS, clicks and visitors are not tracked, and the destination site does not see the referrer that sent you there — so the site you land on cannot easily tell which page or service you came from.

What it actually does

  • Shorten: creates a compact anon.to link you can share.
  • Direct Redirect: sends a visitor straight to a destination URL without storing a short link.
  • Referrer hiding: the destination sees the request as coming without your original referrer.
  • No click tracking: the service says it does not record clicks, visitors or personal data.

Who it is for

It suits people who want a cleaner link for a public post, chat message or document, and who would rather not hand the destination site a trail back to where the link was posted. It is less suited to anyone who needs analytics, custom branded domains, link editing or team dashboards — the point here is the absence of tracking, not campaign measurement.

Trade-offs to weigh

Anonymity cuts both ways. Because nothing is tracked and the referrer is hidden, you also lose the click counts, geography and referral data that normal shorteners provide. And anonymous short links can be used to obscure a destination, which is why cautious recipients sometimes treat unfamiliar short domains with suspicion. If you are the one clicking, the practical precaution is the same as with any shortener: check where you land before entering credentials or payment details.

Practical example

Suppose you want to share a long article link in a public forum but do not want the publisher to see the forum as the traffic source, or to accumulate a profile of who clicked. Pasting the URL into anon.to and sharing the resulting short link achieves that. If instead you are running a campaign and need to know how many people clicked, use a shortener with analytics — anon.to is the wrong tool for that job.

Next step

Decide which you need: privacy or measurement. For privacy, use anon.to's Shorten or Direct Redirect option depending on whether you want a reusable short link or a one-off redirect. For measurement, look at a conventional shortener with click reporting, such as Bitly or a self-hosted option like YOURLS.

How do I shorten a URL anonymously with anon.to?

Paste your long URL into the field on anon.to and choose Shorten. The service creates a short link that redirects to your destination while hiding the referrer, so the destination site does not see where the click came from. It also states that clicks, visitors, and personal data are not tracked, and that redirects run over HTTPS.

If you do not want a stored short link at all, use the Direct Redirect option instead. It redirects any URL anonymously without creating a short link and, according to the site, stores nothing.

Quick comparison

Option What it creates When to use it
Shorten A short link you can share Posting in a chat, forum, or document where a tidy link matters
Direct Redirect No short link, nothing stored One-off visits where you only need to reach the destination privately

Practical notes

  • Anyone with the short link can follow it, so treat the link itself as public even though the referrer is hidden.
  • Anonymity applies to the redirect and referrer, not to what you do on the destination site. If you log in there, that site knows who you are.
  • For sensitive destinations, open the resulting link in a private window or a separate browser profile as an extra layer.

A useful next step: decide first whether you need a shareable link or just a private one-time jump. Choose Shorten for the former, Direct Redirect for the latter.

How does anon.to hide my referrer when I redirect a link?

anon.to hides your referrer by acting as the middle step in the redirect. When you paste a destination URL, the link you share points to anon.to rather than to the final site. A visitor clicks that anon.to link, anon.to issues an HTTP redirect to the destination, and the destination's server sees anon.to as the originating page—not the page or app where the link was originally posted. Because the short link itself is the only address exposed, the original context (your blog, a private message, a forum thread) is not passed along in the Referer header.

The page also states two related behaviors that matter for privacy:

  • No click tracking: anon.to says it does not track clicks, visitors, or personal data.
  • HTTPS redirects: all redirects happen over encrypted connections, so the link between the visitor and anon.to is protected in transit.

Two modes, different exposure

The site offers both a short link and a "Direct Redirect" option. The practical difference is what gets stored and what the visitor sees.

Mode What you share What is stored Best for
Shorten An anon.to short link A mapping from short link to destination Posting a link publicly where you want a tidy, anonymized URL
Direct Redirect A URL that redirects immediately, with no short link created Nothing, according to the site One-off redirects where you do not want a mapping to exist

If your goal is simply to strip the referrer, either mode can work. If your goal is to leave no record of the destination, the Direct Redirect option is the closer fit because the page says no short link is created and nothing is stored.

What this does and does not protect

Referrer hiding protects the source of the click. It does not hide the destination from the visitor, encrypt the destination site itself, or prevent the destination from using its own cookies, logins, or analytics once the visitor arrives. It also does not make you anonymous to anon.to in every sense—the site still receives the request to perform the redirect.

A concrete scenario: you want to share a link in a private group but do not want the destination site to see the group's URL or your username in its referrer logs. Using anon.to means the destination sees an anon.to redirect rather than the group. The trade-off is that the visitor now depends on anon.to being reachable and trustworthy for that click to work.

Next step: decide whether you need the short link at all. If you only want to hide the referrer for a single share, use Direct Redirect; if you want a reusable, postable URL, use Shorten. For broader privacy hygiene, consider a browser that strips referrers by default, such as Brave, or a search engine that does not forward referrer data, such as DuckDuckGo.

What is the difference between shortening a link and using direct redirect on anon.to?

Shortening creates a reusable short link; direct redirect sends you straight through without storing anything.

Shorten turns a long URL into a compact anon.to link you can copy, save, or share. That short link is what others click, and it's the option to use when you want something memorable or postable.

Direct Redirect takes the URL you paste and forwards you to it immediately, with no short link generated and nothing stored. It's a one-time hop, not a link you can hand to someone else.

H3 Practical differences

Shorten Direct Redirect
Output A short anon.to link No link; immediate forward
Reusable Yes, the short link can be clicked again No, it's a single pass-through
Storage The mapping exists so the short link resolves Nothing stored
Best for Sharing in chat, posts, or documents Checking a URL, quick private jumps

Both routes hide the referrer, so the destination doesn't learn where the click came from, and both run over HTTPS.

H3 How to choose

If another person needs to reach the page, use Shorten and send them the short link. If only you need to get there, Direct Redirect avoids leaving a link behind — useful when the destination is sensitive or you simply don't want a persistent record.

One caveat: referrer hiding and no-click-tracking protect you at the redirect layer, but the destination site still sees your IP address and can run its own analytics once you arrive. For stronger separation, pair it with a VPN or private browsing.

Next step: paste the URL into Shorten if you plan to share it, or Direct Redirect if it's a one-off visit. For related privacy tooling, see PrivacyTools and Electronic Frontier Foundation.

Can I use anon.to to share links without the destination site tracking me?

Yes, that's the core purpose. anon.to creates a short link or a direct redirect that hides your referrer, so the destination site doesn't see which page you came from, and anon.to itself states it doesn't track clicks or visitors. It won't make you invisible to the destination site itself, though — once you land there, that site can still log your IP address, set cookies, and run its own analytics. So think of it as removing the "where did this visitor come from" signal, not as full anonymity.

Two modes matter here:

  • Shorten — creates a short link you can share. Useful when you want a compact URL for a chat, forum post, or message.
  • Direct Redirect — redirects straight to the destination without creating a stored short link. Better when you just want to reach a URL without leaving a short-link record behind.

A realistic scenario: you want to send a colleague a link to a competitor's pricing page without that page's analytics attributing the visit to your company's intranet or newsletter. A short link or direct redirect hides that referrer. What it won't hide is that someone from your IP or region visited, or that your colleague's browser carries cookies from a previous session.

Practical decision criteria:

  • Choose anon.to when the concern is referrer leakage or click logging by the shortener.
  • Don't rely on it alone when you need to defeat IP logging, browser fingerprinting, or account-based tracking — pair it with a private browsing session or a VPN.
  • For sharing with non-technical recipients, the short-link mode is friendlier; for your own one-off browsing, direct redirect leaves less behind.

If you want to compare privacy-oriented link tools before committing, look at anon.to itself alongside general-purpose shorteners whose privacy policies you can read directly, and check whether the tool offers a "no stored link" option like the direct redirect described above.

How do I integrate anon.to into my own website or app?

For integration, anon.to points developers to its "Integrate" page rather than documenting an API on the landing page. The practical path is: open that page, look for an endpoint or embed method, and test it with a throwaway link before wiring it into production.

What the page itself confirms

The homepage establishes the behavior you would be integrating, not the mechanics:

  • Two modes. Shorten creates a short link; Direct Redirect sends a visitor straight through without creating or storing a short link.
  • Privacy defaults. Referrer hiding, no click or visitor tracking, and HTTPS on all redirects.
  • A copy-and-go field. The visible example is a single https://anon.to/? input with a Copy button, which suggests a query-parameter style redirect rather than a REST call.

That last point matters most for planning. If redirects work by passing a destination in the URL, you may not need credentials or a server-side client at all — a plain link or a redirect header could be enough.

A concrete test before you build

Take one non-sensitive URL, run it through both modes, and inspect what the browser sends:

  1. Check whether the destination site sees a referrer.
  2. Confirm the short link resolves without a login wall.
  3. Try the same link from a second network to see if results differ.

If those three behave as advertised, integration is mostly a matter of generating the link in your templates or server code.

Trade-offs to weigh

Consideration Why it matters
No tracking You lose click analytics, so pair it with your own server-side logging if you need counts
Referrer hiding Destination sites cannot attribute the traffic to you
Anonymous by design You likely cannot appeal or recover a link if something goes wrong
Third-party dependency Your links break if the service changes or goes down

For a newsletter, a public "share this" button, or any context where you want to shield reader identity, this fits well. For affiliate links, paid campaigns, or anything requiring attribution and reporting, the missing analytics is a real cost.

If you need more control

Self-hosted alternatives give you the same privacy posture with your own domain and logs. Compare options such as GitHub for open-source link shorteners, or a privacy-focused front end like Startpage if your goal is mainly referrer and tracker stripping rather than shortening.

Related questions

More questions →
What Is anon.to? Anonymous URL Shortening and Redirects

anon.to is an anonymous URL shortener and redirect service. It creates short links or performs direct redirects while hiding your referrer, avoiding click tracking, and keeping the destination site from seeing where the visit came from. It's described as free and open, with all redirects served over HTTPS. If you want to share a link without exposing the page you came from or generating trackable click data, anon.to is built for that purpose.

How anon.to works

The service offers two distinct modes, and the difference matters depending on whether you want a reusable link or a one-off redirect.

Short link mode

You submit a URL and anon.to generates a shortened link that points to it. The link can be shared and reused. According to the site, the referrer is hidden and nothing is tracked when someone follows the link.

Direct redirect mode

The site's "Direct Redirect" option redirects any URL anonymously without creating a short link and without storing anything. This is the mode to use when you don't need a persistent short URL — you just want the redirect to happen without leaving a record.

Feature Short link Direct redirect
Creates a reusable short URL Yes No
Stores anything Not stated as stored Explicitly nothing stored
Hides referrer Yes Yes
Tracks clicks No No

What privacy protections it claims

The site lists three specific protections:

  • SSL secured — all redirects happen over encrypted HTTPS connections.
  • No tracking — it states it does not track clicks, visitors, or any personal data.
  • Referrer hiding — destination sites never see where you came from.

These are the service's own claims. They describe what anon.to says it does, not an independent audit, so treat them as the provider's stated behavior rather than a verified guarantee.

When to use it

anon.to fits situations where the source of a click is sensitive or where you don't want a destination site to know which page, app, or platform sent the visitor. For example, if you're sharing a link in a context where you'd rather not reveal the referring page, the referrer-hiding behavior is the relevant feature. If you also want to avoid generating click analytics on the destination side, the no-tracking claim covers that.

Direct redirect is the better choice when you only need the redirect to happen once and don't want a short link persisted. Short link mode is better when the link needs to be shared or reused.

Practical considerations

  • HTTPS is required for the redirect itself, so the transport is encrypted, but that says nothing about what the destination site does with the visit once it arrives.
  • "Free and open" is how the site describes itself, and it links to a GitHub presence. The page evidence does not include pricing details or payment options, so no paid tier is documented here.
  • No account is described as required for the core shortening or redirect functions, though the page shows Login and Register links, which suggests optional accounts may exist for other features.
  • The service cannot control the destination. Hiding the referrer and skipping tracking are things anon.to does on its side; the site you redirect to still handles the visit according to its own policies.

Bottom line

anon.to is a privacy-oriented link tool with two modes: a reusable short link and a no-storage direct redirect. Both claim to hide the referrer and avoid tracking, and both run over HTTPS. Choose direct redirect for one-off anonymous forwarding, and short link mode when you need a shareable link. Verify the current behavior and any account requirements on the site itself, since the privacy claims come from the provider.

Shortening vs. Direct Redirect on anon.to: Which Should You Use?

anon.to offers two distinct ways to anonymize a URL: Shorten, which creates a shareable short link, and Direct Redirect, which forwards you immediately without creating or storing anything. Choose Shorten when you need a link you can send to someone else; choose Direct Redirect when you just want to pass through to a destination once without leaving a trace.

The core difference

Shorten Direct Redirect
What it produces A short link you can copy and share An immediate forward to the destination
Is anything stored? A short link is created Nothing is stored
Best for Sending a link to others A one-time anonymous jump
Referrer handling Hidden Hidden
Tracking None None

Both paths run over encrypted HTTPS and hide your referrer, so destination sites don't see where you came from. The difference is whether a reusable link exists afterward.

When to use Shorten

Use Shorten when the link needs to travel — you're posting it, messaging it, or embedding it somewhere and want the destination hidden behind an anon.to address. The trade-off is that a short link now exists, so it can be reused or shared by anyone who has it.

When to use Direct Redirect

Use Direct Redirect when you only need to reach a destination anonymously right now and don't want a persistent link left behind. Nothing is created and nothing is stored, so there's no artifact to manage or leak. This fits one-off visits where a shareable link would be unnecessary overhead.

How to decide

  • Need to share it later? → Shorten.
  • Just passing through once? → Direct Redirect.
  • Want zero stored artifacts? → Direct Redirect.
  • Want a clean, hide-the-destination link? → Shorten.

A quick example

Suppose you want a colleague to open a page without seeing the original source URL. You'd use Shorten, copy the resulting anon.to link, and send that. If instead you just want to check a page yourself without the destination knowing your referrer, Direct Redirect gets you there and leaves nothing behind.

Both options share the same privacy posture — hidden referrer, no click tracking, HTTPS — so the decision comes down to one question: do you need a link to exist afterward, or not?

Does anon.to Track Clicks or Store Personal Data?

No. According to anon.to's own description, the service does not track clicks, visitors, or any personal data, and its Direct Redirect feature creates no short link and stores nothing. The site presents itself as "privacy-first link shortening," with referrer hiding and HTTPS encryption as core design choices rather than optional settings. If your goal is to pass a link along without generating a record of who clicked it or where they came from, that is exactly what anon.to claims to do.

What anon.to says it does not collect

The homepage makes three specific promises, and they map directly onto the tracking question:

  • No tracking — "We don't track clicks, visitors, or any personal data."
  • Referrer hiding — "Destination sites never see where you came from."
  • No storage on direct redirect — "Redirect any URL anonymously — no short link created, nothing stored."

These are claims about the service's behavior, not independently audited facts. Treat them as the operator's stated policy. The practical takeaway is that anon.to positions itself as the opposite of a typical shortener, which usually logs click counts, timestamps, geolocation, and device data to power analytics dashboards.

How the two modes differ on data retention

The distinction matters because "anon.to doesn't store anything" is only fully true for one of the two modes.

Shorten Direct Redirect
Creates a short link Yes No
Something stored A short-link mapping Nothing, per the site
Referrer hidden Yes Yes
Click tracking None stated None stated
Typical use A link you want to reuse or share widely A one-off anonymous hand-off

With Shorten, a mapping between the short URL and your destination must exist for the redirect to work — otherwise the service couldn't resolve it. The site does not describe what that mapping contains or how long it persists, so the honest reading is: no click tracking, but a link record necessarily exists.

With Direct Redirect, you get a URL of the form https://anon.to/?<your-url> and nothing is created or stored. This is the mode to choose when you want the strongest anonymity claim the site makes.

What "no referrer" actually means for you

Referrer hiding is the part that affects you even if you never think about analytics. When you click a normal link, the destination site can often see the page you came from. That can reveal which forum, chat, or document you were reading. anon.to strips that, so the destination sees an anonymous entry rather than your source page.

This protects the source of the click, not your identity as a visitor. If you are logged into the destination site, it still knows who you are. anon.to hides where you came from, not who you are.

Choosing the right mode

  • Use Direct Redirect when you want a single anonymous hand-off and want nothing stored. This is the mode that matches the "nothing is tracked, nothing is stored" description most completely.
  • Use Shorten when you need a compact, reusable link — for example, posting one URL in several places. Accept that a link mapping exists, even though clicks aren't tracked.
  • Don't rely on either to hide your identity from a site you're logged into, or to protect against a destination that logs IP addresses on its own end. anon.to controls the referrer and its own logging, not the destination's.

Practical caveats worth knowing

  • All redirects run over HTTPS, so the link itself is encrypted in transit.
  • The site lists About, Privacy, Terms, Report, Integrate, and GitHub links, plus Login and Register options — meaning there is an account layer alongside the anonymous tools. Using an account is a separate decision from using the anonymous redirect.
  • The homepage does not state retention periods, logging policies in detail, or jurisdiction. If your threat model requires those specifics, the site's own Privacy page is the place to check before relying on it.
  • "No tracking" is a policy statement from the operator. For high-stakes anonymity, combine it with other measures rather than treating any single shortener as sufficient.

The short answer to the original question: anon.to states it does not track clicks, visitors, or personal data, and its Direct Redirect mode stores nothing at all. Shorten mode necessarily keeps a link mapping but is still described as untracked.

How Does anon.to Keep My Links Anonymous?

anon.to hides your referrer, does not track clicks or visitors, and runs every redirect over encrypted HTTPS. That combination means the destination site cannot see where a visitor came from, and anon.to itself does not build a record of who clicked what. It applies to both of its modes: a shortened link you create, and a "Direct Redirect" that creates no stored short link at all.

The three mechanisms behind the anonymity

1. Referrer hiding

When you click an ordinary link, your browser usually sends a Referer header telling the destination site which page you came from. anon.to strips that. The destination site sees a visitor arriving, but not the page, profile, or community where the link was originally posted.

This matters most in cases where the referring URL itself is identifying — a private forum thread, a ticket page, a document with a token in the URL. Hiding the referrer prevents that URL from leaking to whoever controls the destination site.

2. No click or visitor tracking

anon.to states it does not track clicks, visitors, or any personal data. Practically, that means:

  • No per-click analytics dashboard for the person who created the link.
  • No visitor profiles assembled on anon.to's side.
  • No personal data collected as part of the redirect.

The trade-off is direct: you cannot get click counts or geographic stats from anon.to, because collecting them would contradict the product's purpose.

3. HTTPS on every redirect

All redirects happen over encrypted HTTPS connections. This protects the link in transit between the visitor's browser and anon.to, so the destination of the redirect is not exposed to someone observing the network path.

Short link vs. Direct Redirect

anon.to offers two distinct behaviors, and the privacy properties differ in one important way.

Short link Direct Redirect
What it does Creates a shortened URL that redirects Redirects any URL immediately
Stored on anon.to A short link exists Nothing is stored
Referrer hidden Yes Yes
Click tracking None None
Transport HTTPS HTTPS

The key difference is persistence. A short link has to exist somewhere for the redirect to work, so a mapping between the short code and the destination URL is retained. Direct Redirect creates no short link and stores nothing — it is the better choice when you want a one-off anonymous redirect and do not need a reusable link.

What anon.to does not hide

Anonymity here is about referrer and tracking, not about making you unidentifiable to the destination site itself. If you log into the destination site, or if the destination page runs its own analytics or fingerprinting scripts, those still apply. anon.to removes the referring-page signal and avoids adding its own tracking on top — it does not act as a proxy, VPN, or browser anonymizer.

Similarly, anyone who can see the short link you posted can see the short link. The privacy gain is in what the destination and anon.to learn, not in concealing that a link was shared.

When this is the right tool

anon.to fits situations where the referring page is sensitive or where you simply do not want a third-party shortener logging your audience:

  • Posting a link from a private or invite-only space where the URL itself reveals the source.
  • Sharing a resource without generating click analytics you did not ask for.
  • Needing a quick anonymous redirect with no account and no stored artifact (Direct Redirect).

It is a poor fit if you need click statistics, custom branded domains, or link editing after creation — those require tracking or stored state that anon.to deliberately avoids.

How to Shorten or Redirect a URL with anon.to

Paste your URL into the input field on anon.to, then choose Shorten to create a reusable short link or Direct Redirect to jump to the destination immediately without creating a stored link. Both options hide your referrer and run over HTTPS. The main decision is whether you need a link you can share later (Shorten) or just a one-time anonymous jump (Direct Redirect).

Shorten vs. Direct Redirect

The site offers two distinct modes, and picking the right one depends on whether you need a persistent link.

Shorten Direct Redirect
Creates a short link Yes No
Stores anything Implied by "short link created" Nothing stored
Use case Sharing a link with others One-time anonymous jump
Referrer hidden Yes Yes
Tracking None None

Choose Shorten when you want a link you can copy, save, or send to someone. Choose Direct Redirect when you only need to reach a destination anonymously right now and don't need a link to exist afterward.

How to Shorten a URL

  1. Open anon.to.
  2. Paste your full URL (including https://) into the input field.
  3. Select Shorten.
  4. Wait for the shortening process to complete.
  5. Copy the generated short link.

Expected result: You get a short link you can share. The destination site won't see where visitors came from, and anon.to states it doesn't track clicks or visitors.

Common snag: If the URL is malformed or missing its protocol, shortening may fail. Make sure you paste a complete, working URL.

How to Use Direct Redirect

  1. Open anon.to.
  2. Paste your full URL into the input field.
  3. Select Direct Redirect.
  4. The page generates a redirect URL in the form https://anon.to/?...
  5. Copy it or select Go to jump immediately.

Expected result: You're redirected to the destination anonymously. No short link is created and nothing is stored, per the site's description.

Common snag: Because nothing is stored, you can't retrieve this redirect later — copy the generated URL before navigating away if you need it again.

What "Anonymous" Means Here

anon.to's privacy claims rest on three specific mechanisms:

  • Referrer hiding — destination sites never see the page you came from, so they can't trace the link back to its source.
  • No tracking — the site states it doesn't track clicks, visitors, or personal data.
  • HTTPS — all redirects happen over encrypted connections.

These apply to both Shorten and Direct Redirect. Note that anonymity here concerns the referrer and click data; it doesn't make the destination URL itself secret from anyone who has the link.

Quick Decision Guide

  • Need a shareable link? → Shorten
  • Just need to get there anonymously once? → Direct Redirect
  • Want nothing stored at all? → Direct Redirect
  • Sharing with others who'll click later? → Shorten

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2015, this domain has about 11 years of history. That suggests continuity, although ownership and purpose may have changed. The domain uses the common .to extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. TXT records include verification markers for Google. Such markers may also remain after a service stops being used. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: HSTS, CSP, Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Alpine.js, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Open Graph is partially configured; og:image is missing. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 46 characters, within a common display range. A meta description is present, with 140 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.92.52

Registration details

RDAP / WHOIS

RegistrarTonic
Registered2015-04-13
Expires2027-04-13
Domain statusactive
Nameserversburt.ns.cloudflare.com、tegan.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aanon.to104.21.92.52300—
Aanon.to172.67.186.206300—
AAAAanon.to2606:4700:3031::ac43:bace300—
AAAAanon.to2606:4700:3036::6815:5c34300—
NSanon.toburt.ns.cloudflare.com86400—
NSanon.totegan.ns.cloudflare.com86400—
TXTanon.togoogle-site-verification=T5leVN4Sfz0mqk4S9c30fQfKouVqb89gfF5p55xxRzg300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectanon.to
IssuerGoogle Trust Services
Valid until2026-12-02T15:49 · Remaining when checked: 59 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlmax-age=0, must-revalidate, no-cache, no-store, private
servercloudflare
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff
set-cookieRedacted

Identified technologies

Alpine.jsCloudflare

Pages, Search and Sharing

Meta descriptionShorten and redirect any URL anonymously. anon.to hides your referrer, doesn't track clicks, and keeps your browsing private. Free and open.
Canonical URLhttps://anon.to
LanguageEnglish (default)
Twitter CardNot detected
All bots 0 allowed · 10 disallowed
  • Disallow/login
  • Disallow/register
  • Disallow/forgot-password
  • Disallow/reset-password
  • Disallow/email/
  • Disallow/user/
  • Disallow/two-factor-challenge
  • Disallow/settings
  • Disallow/admin
  • Disallow/my

User reviews (0)

  • No reviews yet.