ecourts.gov.in was registered with whois.registry.in on 8 May 1989 and is hosted on AS4758 National Informatics Centre in India. We couldn't read an SSL certificate for it when we last analysed it. WOT's community rates its safety good (63/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed ecourts.gov.in. Refresh the analysis to check again.
Is ecourts.gov.in’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| India | 99% | 14,986,900 | 12.9% | 87.1% |
| United States | 53% | 80,925 | 100% | 0% |
| United Arab Emirates | 21% | 32,293 | 10.6% | 89.4% |
| Canada | 7% | 10,094 | 100% | 0% |
| Indonesia | 6% | 8,607 | 100% | 0% |
Every IP address ecourts.gov.in resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| ecourts.gov.in | 164.100.129.81 | 0 |
| Host | Name server | TTL |
|---|---|---|
| ecourts.gov.in | ns1.nic.in | 0 |
| ecourts.gov.in | ns10.nic.in | 0 |
| ecourts.gov.in | ns2.nic.in | 0 |
| ecourts.gov.in | ns7.nic.in | 0 |
| Host | Text | TTL |
|---|---|---|
| ecourts.gov.in | "v=spf1 -all" | 0 |
| Host | Policy | TTL |
|---|---|---|
| ecourts.gov.in | 0 issue letsencrypt.org | 0 |
| Host | Start of authority | TTL |
|---|---|---|
| ecourts.gov.in | ns2.nic.in nsadmin.nic.in 2023053103 10800 1800 1209600 14400 | 0 |
No reviews yet. Used ecourts.gov.in? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates ecourts.gov.in good for safety (63/100). We couldn't read an SSL certificate on it when we last analysed it. See Security →
ecourts.gov.in is registered through whois.registry.in. See WHOIS →
ecourts.gov.in was registered on 8 May 1989, making it 37 years old. See Overview →
ecourts.gov.in is served from 1 IP address, mainly on AS4758 National Informatics Centre in India. See Hosting →
Raw registry data for ecourts.gov.in. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.registry.in domain: IN organisation: National Internet Exchange of India address: 6C, 6D, 6E Hansalaya Building 15, Barakhamba Road address: New Delhi 110 001 address: India contact: administrative name: Rajiv Kumar organisation: National Internet Exchange of India address: 6C, 6D, 6E Hansalaya Building 15, Barakhamba Road address: New Delhi 110 001 address: India phone: +91 11 48202011 fax-no: +91 11 48202013 e-mail: [email protected] contact: technical name: Rajiv Kumar organisation: National Internet Exchange of India address: 6C, 6D, 6E Hansalaya Building 15, Barakhamba Road address: New Delhi 110 001 address: India phone: +91 11 48202011 fax-no: +91 11 48202013 e-mail: [email protected] nserver: NS1.REGISTRY.IN 2001:dcd:1:0:0:0:0:12 37.209.192.12 nserver: NS2.REGISTRY.IN 2001:dcd:2:0:0:0:0:12 37.209.194.12 nserver: NS3.REGISTRY.IN 2001:dcd:3:0:0:0:0:12 37.209.196.12 nserver: NS4.REGISTRY.IN 2001:dcd:4:0:0:0:0:12 37.209.198.12 nserver: NS5.REGISTRY.IN 156.154.100.20 2001:502:2eda:0:0:0:0:20 nserver: NS6.REGISTRY.IN 156.154.101.20 2001:502:ad09:0:0:0:0:20 ds-rdata: 25291 8 2 2945b61339dfa7221ad82d5c6c7e3ce4e9c2523e7754acc8131d0ef94617e2f2 whois: whois.registry.in status: ACTIVE remarks: Registration information: http://www.registry.in created: 1989-05-08 changed: 2023-07-25 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with ecourts.gov.in. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.