Register .RU or .SU without a Russian passport?

Comments

• xvps Member

  July 2024 edited July 2024

  @Voltrina said:

  @postcd said:
  Relevant topic: How to register .su (or .ru?) domain without the need to verify my identity?

  That "xUID" service listed at the bottom of the post glows in the dark more than anything i have seen in quite a while. They openly advertise that they allow "phishing, botnets, scampages and spam".

  There is no way that this isn't a honeypot by law enforcement or some fly-by night operation by a group of kids.

  

  

  From $125/month for shared hosting with cPanel.

  @calin is going to create a Russian sub brand when he see these prices.

  There is no way that this isn't a honeypot by law enforcement or some fly-by night operation by a group of kids.

  Well, it's Ruzzian hosting.

  They write: NO Suspension for hosting any kind of content.

  Their terms:

  What we DONT ALLOW :

  Child porn or adult content of any sort. NO Pornographic content at all.
  DDoS/Scanning . FastFlux is not meant for that.
  Drugs or weapon stores or such.
  Mass Mailing on our service.
  Phishing that targets hospitals and miltary service. NOT ALLOWED.
  Projects that harm citizens of Russian Federation directly or indirectly.
  Terrorism or promoting hate speech in any form. NOT ALLOWED.
• ourvds Member

  July 2024

  It’s not possible if you just take a fake scan, but this is fraught with the loss of the domain if there is a check
• totally_not_banned Member

  July 2024 edited July 2024

  @rustelekom said:

  @totally_not_banned said:
  Sure, but who would be more trustworthy in that regard? An actual registrar and the registry itself or some random domain trustee service? Even if i personally wouldn't give either the registrar/registry my passport data or use a trustee service i'd say it's the former and the second option also always comes with the risk of loosing the domain if the service operators decide to rather take the domain for themself. What recurse would you really have? The domain isn't registered in your name after all. While i absolutely love whois privacy i'd never use any of the various trustee services without a very good reason.

  Legally registered services can be trusted. However, due to the large amount of leaked data, customers will often refuse to comply with KYC requests.
  This is a big problem for providers who want to offer anything to customers. Because they have to request verification from the state for customers using the KYC procedure.

  We have working options for Russian citizens, but they are restricted and costly (for providers). However, theoretically, this could be a solution. Since customers do not need to host personal data, and the hoster does not need them in this case, the host only uses a unique token provided by the customer and generated for each account, which is verified by the state registry. In this way, all requirements are met, and customer private data is safe and stored only in one place - the state registry.

  Work in the same way as 2-way authorization. Of customer must have account in state registry but in Russia most of people already has it. Foreigners who live in Russia temporarily or permanently may also register an account with the state registry.

  Well, yes, in regards to data safety something like that might be advantageous. The downside is that there's a lot of centralized profiling data being collected (i.e. who uses what where) and that isn't something i like too much either. Sure from an idealistic viewpoint one could say that it's at least stored with an official agency but then i don't like involving the state in my personal life. That's obviously a very subjective view on things and other people might have different priorities.

  In general i don't mind giving my name/address (that data has been out there for a long time already anyways and while i can't check i'll just assume it having been passed on and sold 100s of times by now) but when it comes to official documents it's better for something i want very, very much, since otherwise i'll look elsewhere. I mean it's not impossible to make sending ID scans somewhat save - just redact everything not 100% required and watermark the living shit out of the picture so it hopefully can't be used for anything else should it leak out but it's quite a bit of work and there's always a little bit of risk remaining.