rgukt.in valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | |
| Description | N/A |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 119.18.54.130 |
| Location | India |
Related Websites
| Site | Rank |
More to Explore
rgukt.in Valuation
|
US$3,564,003
Last updated:
rgukt.in has Semrush global rank of 2,969,780. rgukt.in has an estimated worth of US$ 3,564,003, based on its estimated Ads revenue. rgukt.in receives approximately 411,232 unique visitors each day. Its web server is located in India, with IP address 119.18.54.130. According to SiteAdvisor, rgukt.in is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$3,564,003 |
| Daily Ads Revenue | US$3,290 |
| Monthly Ads Revenue | US$98,696 |
| Yearly Ads Revenue | US$1,184,346 |
| Daily Unique Visitors | 27,416 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| rgukt.in. | A | 298 | IP: 119.18.54.130 |
| rgukt.in. | NS | 86400 | NS Record: cora.ns.cloudflare.com. |
| rgukt.in. | NS | 86400 | NS Record: hal.ns.cloudflare.com. |
| rgukt.in. | MX | 300 | MX Record: 0 aspmx2.googlemail.com. |
| rgukt.in. | MX | 300 | MX Record: 0 aspmx.l.google.com. |
| rgukt.in. | MX | 300 | MX Record: 0 aspmx3.googlemail.com. |
| rgukt.in. | MX | 300 | MX Record: 0 alt2.aspmx.l.google.com. |
| rgukt.in. | MX | 300 | MX Record: 0 aspmx5.googlemail.com. |
| rgukt.in. | MX | 300 | MX Record: 0 alt1.aspmx.l.google.com. |
| rgukt.in. | MX | 300 | MX Record: 0 aspmx4.googlemail.com. |
| rgukt.in. | TXT | 300 | TXT Record: google-site-verification=VbjkamEeJVdf6xbC2vPIMpdHEhmQWtWKPK46GDjMK50 |
HTTP Headers
HTTP/1.1 302 Found Date: Fri, 22 Oct 2021 10:11:16 GMT Server: Apache Content-Security-Policy: upgrade-insecure-requests; Location: https://rgukt.in/ Content-Type: text/html; charset=iso-8859-1 HTTP/2 200 date: Fri, 22 Oct 2021 10:11:17 GMT server: Apache content-security-policy: upgrade-insecure-requests; accept-ranges: none content-type: text/html; charset=UTF-8 |