Whowaswho-indology.info
Persons of Indian Studies by Prof. Dr. Klaus Karttunen – भारतीय अध्ययन से संबद्ध व्यक्ति
Domain Summary
What is the traffic rank for Whowaswho-indology.info?
• Whowaswho-indology.info ranks #6,724,823 globally on HypeStat.
What percent of global Internet users visit Whowaswho-indology.info?
• 6.0E-7% of global Internet users visit Whowaswho-indology.info
How many people visit Whowaswho-indology.info each day?
• Whowaswho-indology.info receives approximately 28 visitors and 38 page impressions per day.
How much Whowaswho-indology.info can earn?
• Whowaswho-indology.info should earn about $0.16/day from advertising revenue.
What is Whowaswho-indology.info estimated value?
• Estimated value of Whowaswho-indology.info is $158.19.
What IP addresses does Whowaswho-indology.info resolve to?
• Whowaswho-indology.info resolves to the IP addresses 134.76.9.14.
Where are Whowaswho-indology.info servers located in?
• Whowaswho-indology.info has servers located in Göttingen, Lower Saxony, 37077, Germany.
whowaswho-indology.info Profile

What technologies does whowaswho-indology.info use?
These are the technologies used at whowaswho-indology.info. whowaswho-indology.info has a total of 7 technologies installed in 10 different categories.whowaswho-indology.info Traffic Analysis
Whowaswho-indology.info is ranked #6,724,823 in the world. This website is viewed by an estimated 28 visitors daily, generating a total of 38 pageviews. This equates to about 848.4 monthly visitors. Whowaswho-indology.info traffic has increased by 8.1% compared to last month.Daily Visitors28
19.59%
Monthly Visits848.4
8.1%
Pages per Visit1.38
6.42%
Visit duration11:12
11100%
Bounce Rate80.89%
15.01%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 28
- Monthly Visits:
- 848
- Pages per Visit:
- 1.38
- Daily Pageviews:
- 38
- Avg. visit duration:
- 11:12
- Bounce rate:
- 80.89%
- Global Reach:
- 6.0E-7%
- Monthly Visits (SEMrush):
- 827
- Monthly Unique Visitors (SEMrush):
- 353
- HypeRank:
- 6,724,823
- SEMrush Rank:
- 6,791,230
- SimilarWeb Rank:
- 6,724,823
Traffic sources
- Direct:
- 19.11%
- Referral:
- 57.32%
- Search:
- 23.58%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 100.00%
- Mobile:
- 0%
Total Visits Last 3 Months
1.6K
FEB
784.8
MAR
848.4
APR
Backlinks Report ▼
Whowaswho-indology.info has a total of 3,707 backlinks from 251 referring domains and most of them comes from United States.- Total Backlinks:
- 3,707
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 251
- Referring IPs:
- 276
- Authority Domain Score:
- 17
Backlinks by country
- Country
- Domains
- United States 54
- Germany 17
- France 11
- United Kingdom 9
- Russian Federation 6
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 102
- .org
- 30
- .net
- 15
- .edu
- 3
- .gov
- 0
Last update was 36 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with whowaswho-indology.info in any way. Only publicly available statistics data are displayed.
Search Engine Indexes ▼
Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.- Google Index:
- 9,540
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- whowaswho-indology.info
- Rank:
(Rank based on keywords, cost and organic traffic) - 6,791,230
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 142
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 15
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $0.00
Revenue report ▼
Google.com would generate approximately $0.2 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $4.8 and annual gross revenue of approximately $58.4. Based on these figures, the site's net worth is estimated at around $158.2.How much would whowaswho-indology.info make?
- Daily Revenue:
- $0.16
- Monthly Revenue:
- $4.80
- Yearly Revenue:
- $58.40
How much is whowaswho-indology.info worth?
- Website Value:
- $158.2
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- whowaswho-indology.info
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Desktop summary
- Root domain:
- whowaswho-indology.info
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Abusive Experience Report ▼
Summary of the abusive experience rating of a website.- Root domain:
- whowaswho-indology.info
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Not reviewed
Where is whowaswho-indology.info hosted? ▼
Whowaswho-indology.info may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 134.76.9.14
- ASN:
- AS207592
- ISP:
- Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH, Goettingen
- Server Location:
- Göttingen
Lower Saxony, NI
37077
Germany, DE
Other sites hosted on 134.76.9.14
How fast does whowaswho-indology.info load? ▼
The average loading time of whowaswho-indology.info is 499 ms. The Desktop speed index is 99 and mobile speed index is 97.- Average Load Time:
- 499 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.4s
First Contentful Paint (FCP)2.0s
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)2.0s
Origin Data
All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.4s
First Contentful Paint (FCP)2.0s
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)2.0s
Lab Data
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Largest Contentful Paint 0.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive 1.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.5s
First Contentful Paint (FCP)2.2s
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)2.2s
Origin Data
All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)1.5s
First Contentful Paint (FCP)2.2s
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)2.2s
Lab Data
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Time to Interactive 4.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Speed Index 4.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Does whowaswho-indology.info use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on whowaswho-indology.info are reduced by 72%.
whowaswho-indology.info use gzip compression.
Original size: 23.24 KB
Compressed size: 6.48 KB
File reduced by: 16.76 KB (72%)
Compressed size: 6.48 KB
File reduced by: 16.76 KB (72%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. whowaswho-indology.info supports HTTPS. whowaswho-indology.info supports HTTPS
Verifying SSL Support. Please wait...
Common Name: vwebfile.gwdg.de
Organization: "Gesell. f\C3\BCr wissenschaftliche Datenverarbeitung mbH, G\C3\B6ttingen"
Location: Niedersachsen, DE
Issuer: Sectigo RSA Organization Validation Secure Server CA
Valid from: Dec 20 00:00:00 2024 GMT
Valid until: Dec 20 23:59:59 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization: "Gesell. f\C3\BCr wissenschaftliche Datenverarbeitung mbH, G\C3\B6ttingen"
Location: Niedersachsen, DE
Issuer: Sectigo RSA Organization Validation Secure Server CA
Valid from: Dec 20 00:00:00 2024 GMT
Valid until: Dec 20 23:59:59 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Sectigo RSA Organization Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: USERTrust RSA Certification Authority
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Issuer: AAA Certificate Services
Valid from: Mar 12 00:00:00 2019 GMT
Valid until: Dec 31 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Issuer: AAA Certificate Services
Valid from: Mar 12 00:00:00 2019 GMT
Valid until: Dec 31 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. whowaswho-indology.info supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.server: nginx
date: Sat, 10 May 2025 21:28:23 GMT
content-type: text/html; charset=UTF-8
content-length: 6637
link: <https://whowaswho-indology.info/wp-json/>; rel="https://api.w.org/"
link: <https://whowaswho-indology.info/wp-json/wp/v2/pages/6223>; rel="alternate"; type="application/json"
link: <https://whowaswho-indology.info/>; rel=shortlink
vary: Accept-Encoding
content-encoding: gzip
DNS Lookup ▼
DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.Type | Ip | Target/Txt | TTL |
SOA | 60 | ||
Mname | dns1.gwdg.de | ||
Rname | hostmaster.gwdg.de | ||
Serial Number | 679233809 | ||
Refresh | 21600 | ||
Retry | 3600 | ||
Expire | 2419200 | ||
Minimum TTL | 3600 | ||
A | 134.76.9.14 | 3521 | |
NS | 3521 | ||
NS | 3521 | ||
NS | 3521 |
Whois Lookup ▼
Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on April 24, 2017 and will expire on April 24, 2026 if not renewed. This website is now assigned through the registrar COREhub, S.R.L.. The WHOIS data for this website's domain was last updated on April 24, 2025.- Domain Created:
- 2017-04-24
- Domain Expires:
- 2026-04-24
- Domain Updated:
- 2025-04-24
- Domain Age:
- 8 years 1 months 22 days
- Domain Registrar:
- COREhub, S.R.L.
- Domain Owner:
- Georg-August-Universitaet Goettingen
- WhoIs:
Domain Name: whowaswho-indology.info Registry Domain ID: 716309f4cd0c40d88088a12a615a3cc9-DONUTS Registrar WHOIS Server: corenic.org/whois Registrar URL: http://corenic.org Updated Date: 2025-04-24T16:28:51Z Creation Date: 2017-04-24T16:28:50Z Registry Expiry Date: 2026-04-24T16:28:50Z Registrar: COREhub, S.R.L. Registrar IANA ID: 15 Registrar Abuse Contact Email:Registrar Abuse Contact Phone: +34.935275235 Domain Status: autoRenewPeriod https://icann.org/epp#autoRenewPeriod Registry Registrant ID: REDACTED Registrant Name: REDACTED Registrant Organization: Georg-August-Universitaet Goettingen Registrant Street: REDACTED Registrant City: REDACTED Registrant State/Province: Registrant Postal Code: REDACTED Registrant Country: DE Registrant Phone: REDACTED Registrant Phone Ext: REDACTED Registrant Fax: REDACTED Registrant Fax Ext: REDACTED Registrant Email: REDACTED Registry Admin ID: REDACTED Admin Name: REDACTED Admin Organization: REDACTED Admin Street: REDACTED Admin City: REDACTED Admin State/Province: REDACTED Admin Postal Code: REDACTED Admin Country: REDACTED Admin Phone: REDACTED Admin Phone Ext: REDACTED Admin Fax: REDACTED Admin Fax Ext: REDACTED Admin Email: REDACTED Registry Tech ID: REDACTED Tech Name: REDACTED Tech Organization: REDACTED Tech Street: REDACTED Tech City: REDACTED Tech State/Province: REDACTED Tech Postal Code: REDACTED Tech Country: REDACTED Tech Phone: REDACTED Tech Phone Ext: REDACTED Tech Fax: REDACTED Tech Fax Ext: REDACTED Tech Email: REDACTED Name Server: dns1.gwdg.de Name Server: dns2.gwdg.de Name Server: dns3.gwdg.de DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2025-05-10T21:29:40Z