The brains behind the website that apparently leaked user details of 120 million Reliance Jio subscribers on Sunday-- are yet to be identified. Meanwhile, the telco's claim that the data breach was "inauthentic" has been challenged by many Jio users, who said they had found their credentials on the website, before it was taken down by the hosting provider.

Many Reliance Jio users in India reported on Sunday night that had access to sensitive customer details, including mobile numbers, email IDs, first name, last name, SIM activation date and the location from where the connection was activated. The data breach has likely affected all Reliance Jio users and the company currently has over 100 million subscribers.

Reliance Jio
An employee arranges a display for JioFi devices at a Reliance Digital store in Mumbai on April 21, 2017.INDRANIL MUKHERJEE/AFP/Getty Images

"We have come across the unverified and unsubstantiated claims of the website and are investigating it. Prima facie, the data appears to be inauthentic. We want to assure our subscribers that their data is safe and maintained with highest security," Reliance Jio said in a statement.

Many people, however, took to Twitter and said Jio's claim was not true.

Various reports also confirmed the data breach.

We've done a bit of digging to track down The research showed the website was registered in India. However, the people behind the website are still unknown.

Reliance Jio data leaked
In picture: The Aadhaar number of Reliance Jio users whose data has been leaked was not visible on

Here's the details about we've got from, an online tool that offers a comprehensive report on any website or I.P. address, including the hosting provider, the physical location of the website, the IP Address history and the DNS information.

Some key information about

  • Registered on: 18 May 2017
  • Last Updated on: 18 May 2017
  • Expires on: 18 May 2018
  • IP Address:
  • IP Location: India
  • IP Reverse DNS (Host):
  • Hosting Company: P.d.r Solutions Fzc
  • Website Nameservers: NS1.CP-IN-10.WEBHOSTBOX.NET / NS2.CP-IN-10.WEBHOSTBOX.NET

Though is currently inaccessible, it doesn't necessarily mean the leak never happened, or the leaked data will not surface again.