Website profiles · Technology insights · Alternatives

rimgo.codeberg.page

No paid content found
Visit website
Profile views 10 Outbound visits 4 Normal
Loading InstancePage... Full homepage screenshot

At a glance

Category
Other
Language
English
Paid-content signal
No paid content foundObserved
Registered
2020
Hosting
Individual Network Berlin (IN-Berlin) e.V.Inferred
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 Rimgo?

Rimgo is a privacy-focused front end for Imgur. It lets you browse and view Imgur-hosted images and albums through a different interface, so you can look at content without loading Imgur's own pages. The instance page you're looking at is a directory that helps you find a Rimgo server to use.

The page groups available instances into standard, Tor, and i2p categories. The standard list is for everyday browsing. The Tor and i2p entries are aimed at people who want stronger anonymity, but they only work if you're already using Tor Browser or a browser configured for i2p. That's a real trade-off: more privacy usually means slower loading and extra setup.

How to choose

  • If you just want to view Imgur links without Imgur's trackers and clutter, pick a normal instance from the "All" list.
  • If anonymity matters more than speed, use a Tor or i2p instance with the matching browser.
  • If one instance is slow or down, try another; these are community-run, so reliability varies.

A practical next step is to open the "All" list, pick an instance that responds quickly, and bookmark it for when you encounter Imgur links.

How do I use Rimgo to view Instagram content anonymously?

Rimgo is an alternative front end for Instagram: instead of loading Instagram's own site and its trackers, you open a Rimgo instance and view the same public content through that server. The instance at Rimgo is a directory page rather than a single working front end — its job is to point you at an instance to use.

How to actually get started

  1. Open the instance page and pick an entry from the list.
  2. Use the "Random Selection" option if you just want a working instance without choosing; otherwise pick from the general list.
  3. Once on a chosen instance, replace the Instagram URL in your address bar with the Rimgo equivalent, or paste the Instagram link into the instance's search/URL field.
  4. Browse profiles, posts and Reels as normal. Public content is what an Instagram front end can serve; anything behind a login generally is not available.

Matching the instance type to your threat model

Instance type Privacy gain What you need Practical trade-off
Standard instances Hides your visit from Instagram's own front end A normal browser Your traffic still goes to the instance operator
Tor instances Adds network-level anonymity Tor Browser Slower, some instances go offline, media loads poorly
i2p instances Adds network-level anonymity over i2p A browser configured for i2p Fewer instances, more setup, slower

The page's own wording is that Tor instances "provide improved privacy but require the use of Tor Browser," and i2p instances likewise require a browser configured for i2p. That is the key decision: if you only want to avoid Instagram's trackers and ads, a standard instance is enough. If you also want to hide from your network or ISP that you are viewing Instagram content, you need Tor or i2p — and you should accept a slower, flakier experience.

A concrete scenario

Say you want to check a public account's recent posts without logging in and without Instagram building a profile of your visit. You open the Rimgo instance list, pick a standard instance, paste the profile URL, and read the posts. Your browser never talks to Instagram, but the instance operator can see what you requested. If that matters to you — for example, on a shared or monitored network — switch to a Tor instance and open it in Tor Browser instead.

A practical next step

Try one standard instance first to confirm the content you want is actually reachable, then move to a Tor or i2p instance only if you need network-level anonymity. If you want the same approach for other platforms, the same project family covers them: ProxiGram for Instagram-adjacent use, LibReddit for Reddit, Invidious for YouTube and Nitter for X/Twitter.

Two caveats worth knowing before you rely on it: this is a community-run directory, so individual instances can disappear or rate-limit, and a front end changes who sees your request — it does not make you anonymous by itself unless you also use Tor or i2p.

What is the difference between Rimgo's Tor instances and i2p instances?

Both are privacy-focused ways to reach Rimgo, but they differ in the network you must use to connect. Tor instances require the Tor Browser; i2p instances require a browser configured for i2p. The Rimgo page groups them separately under "Tor instances" and "i2p instances," and also offers a "Random Selection" plus an "All" view.

In practice, the choice is less about Rimgo itself and more about which anonymity network you already trust and have set up. If you use Tor regularly, Tor instances are the simpler path. If you run an i2p router and have a browser pointed at it, i2p instances fit that workflow.

A quick way to decide: pick the network you can already browse reliably. If you have neither, Tor Browser is generally the more common starting point, while i2p suits users who specifically want its network model. You can compare the available options directly at Rimgo.

Why does Rimgo require Tor Browser or an i2p-configured browser?

Rimgo doesn't require Tor Browser or an i2p-configured browser for all of its instances. The requirement applies specifically to the Tor and i2p instance categories listed on the page. The standard "All" list includes regular instances that work in any browser.

The reason is architectural: those particular instances are hosted as Tor hidden services or i2p services. A hidden service only resolves inside its own anonymity network, so a normal browser can't reach the address at all. You need Tor Browser (or a browser routed through Tor) to reach a .onion address, and a browser configured for i2p to reach an i2p address. The privacy benefit is mutual: the instance operator doesn't need a clearnet domain, and your connection to it isn't visible to your ISP or a conventional DNS resolver.

Choosing an instance type

Instance type Browser needed Main trade-off
Standard ("All") Any modern browser Fastest and simplest; your access to the instance is visible to your network
Tor Tor Browser or Tor-routed browser Stronger anonymity; slower, and some media or large pages may load poorly
i2p Browser configured for i2p Anonymity within the i2p network; smaller network, fewer users, more setup

Rimgo is a privacy-focused front end for Imgur-style content, so the instance list is essentially a menu of how much network-level privacy you want to trade for speed and convenience.

A practical next step

If you just want to browse without setup, pick an instance from the "All" list. If hiding your browsing from your ISP matters more than speed, use Tor Browser and choose a Tor instance. If you already run i2p, use an i2p instance instead — but don't install i2p solely for this, since the setup effort rarely pays off unless you use the network for other things.

One caveat: third-party instances are run by volunteers, so availability and content policies vary. Treat any single instance as replaceable rather than as a dependable long-term service.

How do I find a working Rimgo instance when one is down?

Use the instance list to switch to another public Rimgo server, or to a Tor or i2p instance if you need privacy. Rimgo is a front-end that lets you view Imgur content without visiting Imgur directly, so when one instance is down you are not limited to that one address.

The page groups options into:

  • Random Selection – pick a random working instance.
  • All – browse the full list of public instances.
  • Tor instances – better privacy, but you need Tor Browser.
  • i2p instances – better privacy, but you need a browser configured for i2p.

Practical next step: open the instance list, try the Random Selection first, and if it fails, open a few entries from All in separate tabs. Keep two or three working addresses bookmarked so you can switch quickly next time.

How to choose:

  • If you just want to load a link quickly, use a public instance from All.
  • If you want to avoid exposing your normal connection, use a Tor instance with Tor Browser.
  • If you already use i2p, use an i2p instance; otherwise the setup is not worth it for a one-off visit.

One caveat: public instances can go down, be rate-limited, or be blocked by your network. If every public instance fails, the problem may be your connection, a regional block, or Imgur itself rather than Rimgo. In that case, try a different network or use Tor.

For background on the project and its official instance list, see Codeberg.

Is Rimgo safe and what privacy benefits does it offer compared to Instagram?

Rimgo is a privacy-oriented front end for Instagram, not a replacement account or app. Its main safety value is that you browse through a third-party instance instead of Instagram's own site, which can reduce direct tracking by Instagram and let you avoid logging in. The trade-off is that you are trusting whoever runs that instance, and the instance list itself notes that Tor and i2p options require Tor Browser or an i2p-configured browser.

What Rimgo changes

  • No Instagram account required. You can view public profiles and posts without handing Instagram your login.
  • Reduced direct tracking. Requests go to the Rimgo instance, not straight to Instagram's app or site, so Instagram sees less of your browsing context.
  • Tor and i2p instances. These provide improved privacy by routing traffic through anonymity networks, but only if you use Tor Browser or an i2p-configured browser as noted on the page.
  • Random instance selection. The page offers a random selection option, which can spread your usage across instances rather than always using one.

Safety caveats

Rimgo's safety depends almost entirely on the instance operator. A malicious or poorly maintained instance could log your requests, inject content, or go offline without warning. The official Rimgo project does not control every public instance. For sensitive browsing, prefer a Tor or i2p instance, and remember that anyone operating the instance can still see the traffic that reaches it.

Practical comparison

Aspect Instagram Rimgo
Login required Usually yes for full use No
Direct Instagram tracking High Reduced
Trust required Instagram/Meta Instance operator
Anonymity network support No Tor and i2p instances listed
Content completeness Full app features Public content only, dependent on instance

Next step

If you only need to view public Instagram content without logging in, start with a Tor instance in Tor Browser. If you need to post, message, or use stories, Rimgo will not replace Instagram. For a broader privacy front-end ecosystem, compare with Libreddit or Invidious, which apply the same instance-based model to Reddit and YouTube.

Related questions

More questions →
Do I need special software to use instances listed on rimgo.codeberg.page?

It depends on which instance you pick. The page groups its listings into All, Tor instances, and i2p instances. Plain instances under "All" are meant to be opened in a normal browser. The Tor and i2p groups are explicitly described on the page as requiring extra software: Tor instances "provide improved privacy but require the use of Tor Browser," and i2p instances "provide improved privacy but require the use of a browser configured to use i2p." So the answer is: no special software for the general list, but yes for the privacy-network lists.

What each instance group requires

Instance group Extra software needed? What the page says
All No Listed as general instances; open in a regular browser
Tor instances Yes — Tor Browser "provide improved privacy but require the use of Tor Browser"
i2p instances Yes — an i2p-configured browser "provide improved privacy but require the use of a browser configured to use i2p"

The page also offers a 🔮 Random Selection option, which picks an instance for you. If that random pick lands on a Tor or i2p address, the same software requirement applies — the random button doesn't bypass the network requirement.

How to decide before you click

  1. Check your environment first. If you only have a standard browser (Chrome, Firefox, Safari, Edge) with no Tor or i2p setup, stay in the "All" group.
  2. Pick from "All" if you just want to reach an instance quickly. These are the entries intended for ordinary browsing.
  3. Choose a Tor instance only if you already run Tor Browser. A .onion-style address won't resolve in a normal browser, so the link will simply fail rather than load slowly.
  4. Choose an i2p instance only if your browser is configured for i2p. Without that configuration, the address is unreachable.
  5. Use Random Selection only when you're fine with whatever group it returns — otherwise select manually from the group that matches your setup.

Common snags

  • A Tor or i2p link "does nothing" in a normal browser. That's expected, not a broken instance — the address type requires the matching network software.
  • Installing Tor Browser is not the same as configuring i2p. They're separate tools; having one doesn't cover the other group.
  • Privacy vs. convenience. The page frames Tor and i2p as privacy improvements that come with a software requirement. If you don't need that trade-off, the "All" list is the simpler path.

Bottom line

Match the instance group to what you already have installed: "All" for a standard browser, Tor instances only with Tor Browser, i2p instances only with an i2p-configured browser. If you're unsure, start with "All" and avoid Random Selection until your setup can handle every group it might return.

How do I find and open a rimgo instance from rimgo.codeberg.page?

rimgo.codeberg.page is an instance directory, not a single working rimgo site. To reach an actual rimgo instance, open the page and use one of its four entry points: 🔮 Random Selection for an instant random redirect, All to browse every listed instance, Tor instances for onion addresses that require Tor Browser, or i2p instances for addresses that require an i2p-configured browser. Clicking any listed instance takes you to that instance's own domain.

What the page actually gives you

The directory groups instances by how they are reached, and each group carries a different requirement:

Entry point What it does What you need
🔮 Random Selection Sends you to one instance chosen at random Nothing beyond a normal browser
All Shows the full list of instances Nothing beyond a normal browser
Tor instances Lists instances reachable over Tor Tor Browser
i2p instances Lists instances reachable over i2p A browser configured for i2p

The page states plainly that Tor instances "provide improved privacy but require the use of Tor Browser," and that i2p instances "provide improved privacy but require the use of a browser configured to use i2p." So the privacy benefit comes with a setup cost — if you do not already have Tor Browser or an i2p-capable browser, those two groups will not open for you.

Opening an instance step by step

  1. Load rimgo.codeberg.page in your browser.
  2. Choose one of the four options:
    • Click 🔮 Random Selection if you just want a working instance and do not care which one.
    • Click All if you want to see every instance and pick deliberately.
    • Click Tor instances if you already run Tor Browser.
    • Click i2p instances if your browser is configured for i2p.
  3. Click the specific instance link you want (or let Random Selection redirect you).
  4. You land on that instance's own address — that is where you actually use rimgo.

Expected result: your browser leaves the directory and loads the chosen instance's homepage. If nothing loads, the instance itself is likely down or blocked on your network; go back and pick another.

Choosing between the groups

  • Want the fastest path? Use 🔮 Random Selection. It removes the decision, but you get no say in which instance you land on.
  • Want control? Use All and pick from the list. This is the better choice if a specific instance has failed for you before.
  • Need stronger privacy and already have the tooling? Use Tor instances or i2p instances. Only pick these if Tor Browser or an i2p-configured browser is already set up — otherwise the links will not resolve.
  • On a restricted network? The Tor and i2p groups exist precisely because direct access can be blocked, but they only help if you have the matching browser.

Common snags

  • Treating the directory as the service. rimgo.codeberg.page only points you elsewhere; the actual rimgo front end lives on the instance you click.
  • Clicking a Tor or i2p link in a normal browser. It will fail. Match the browser to the group.
  • Assuming one instance speaks for all. Instances are independent, so availability and behavior can differ between them. If one does not respond, try another from the All list or re-run Random Selection.
What Is rimgo.codeberg.page?

rimgo.codeberg.page is a directory page for rimgo instances. It presents a random selection entry point and lists public instances grouped by network type: standard instances, Tor instances, and i2p instances. It is not itself a full rimgo frontend for browsing content; it is the page you use to find and pick an instance. If you already know which instance you want, you can skip this page entirely. If you want a privacy-friendly alternative frontend and don't know where to start, this page is the starting point.

What the page actually offers

The page is organized around four headings:

  • 🔮 Random Selection — a single entry point that sends you to a randomly chosen instance.
  • All — the general list of public instances.
  • Tor instances — instances reachable only through Tor.
  • i2p instances — instances reachable only through an i2p-configured browser.

The page's own description states the trade-off directly: Tor instances "provide improved privacy but require the use of Tor Browser," and i2p instances "provide improved privacy but require the use of a browser configured to use i2p."

Choosing between the three groups

Group Reachable with Privacy level When to use it
All A normal browser Standard You just want a working instance fast
Tor instances Tor Browser Improved You want traffic routed through Tor and already have Tor Browser
i2p instances A browser configured for i2p Improved You already use i2p and want to stay inside that network

The key decision is not which instance is "best" but which network you are already set up to use. A Tor instance is useless if you open it in a regular browser, and the same applies to i2p instances. Match the instance group to the browser you actually have.

How to use it

  1. Open rimgo.codeberg.page.
  2. If you don't care which instance you get, use 🔮 Random Selection.
  3. If you want a specific network, pick from All, Tor instances, or i2p instances according to your browser setup.
  4. Follow the instance link and use rimgo from there.

Expected result: you land on a working rimgo instance rather than a dead or unreachable one.

Common sticking points

  • Using a Tor or i2p instance in a normal browser. It will not load. The network requirement is real, not optional.
  • Treating the directory as the service. This page lists instances; the actual frontend behavior happens after you follow a link.
  • Assuming all instances behave identically. They are separate deployments, so availability and uptime can differ. If one fails, try another from the same group.

The short version

Use rimgo.codeberg.page when you need to find a rimgo instance and don't have one bookmarked. Pick Random Selection for speed, All for a standard browser, or the Tor / i2p groups if you already run those networks. The page's only job is to get you to an instance that matches your setup.

Website Overview

Limited stack disclosure and few obvious backend markers suggest a more restrained public footprint. That reduces easy fingerprinting clues but is not proof of overall security. 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 2020, this domain has about 6 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is Gandi SAS, a widely used domain service provider. The domain uses the common .page extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by desec.io, indicating managed DNS hosting. DNSSEC is enabled, allowing validating resolvers to authenticate signed DNS data. CAA records restrict which certificate authorities are authorized to issue certificates. 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.

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 by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Permissions-Policy, clickjacking protection. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The via 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 contains the custom value git-pages (git-pages), pages-server.

Technology Stack Analysis

No obvious technology stack is exposed. This may reflect restrained information disclosure, although the underlying technologies remain unknown.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 23 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSdesec.io
HostingIndividual Network Berlin (IN-Berlin) e.V.
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Germany flagBerlin, State of Berlin, Germany Inferred 217.197.84.141

Registration details

RDAP / WHOIS

RegistrarGandi SAS
Registered2020-10-07
Expires2030-10-07
Domain statusclient transfer prohibited
Nameserversns1.desec.io、ns2.desec.org
DNSSECsigned

DNS records

DNS

TypeNameValueTTLPriority
Arimgo.codeberg.page217.197.84.1413600—
AAAArimgo.codeberg.page2a0a:4580:103f:c0de::23600—
NScodeberg.pagens1.desec.io3600—
NScodeberg.pagens2.desec.org3600—
CAAcodeberg.page128 iodef "mailto:[email protected]"3600—
CAAcodeberg.page128 issue "letsencrypt.org;accounturi=https://acme-staging-v02.api.letsencrypt.org/acme/acct/193562844;validationmethods=dns-01"3600—
CAAcodeberg.page128 issue "letsencrypt.org;accounturi=https://acme-staging-v02.api.letsencrypt.org/acme/acct/272029763;validationmethods=tls-alpn-01,http-01"3600—
CAAcodeberg.page128 issue "letsencrypt.org;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/292520050;validationmethods=tls-alpn-01,http-01"3600—
CAAcodeberg.page128 issue "letsencrypt.org;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/3580806161;validationmethods=dns-01"3600—
CAAcodeberg.page128 issuemail ";"3600—
CAAcodeberg.page128 issuevmc ";"3600—
DScodeberg.page51530 13 2 cd0f18a061debe176e0544bd392c798c0abde83069dec1c5c75fd5fd5817aa801800—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subject*.codeberg.page
IssuerLet's Encrypt
Valid until2026-12-10T15:28 · Remaining when checked: 70 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlpublic, max-age=600
servergit-pages (git-pages), pages-server
strict-transport-securitymax-age=63072000; includeSubdomains; preload
referrer-policystrict-origin-when-cross-origin

Identified technologies

Technology stack: Unknown

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

Unknown

No sitemaps found

User reviews (0)

  • No reviews yet.