Drsinha.com
Drsinha is ranked > 3,000,000 in the United Kingdom. 'Pradeep K Sinha MD PhD FACS Otolaryngology Nasal, Sinus and Sleep ..'
--Rank in United Kingdom
29,625,689Worldwide Rank
| Monthly pages viewed | 227 | |
| Monthly visits | 227 | |
| Value per visitor | -- | |
| Estimated worth | £351.79 | |
| External links | 27 | |
| Number of pages | 255 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Visitors
| Traffic History 90 Day Average | ||
| Worldwide Rank | 24,895,537 |  6,691,423 |
|---|---|---|
| Daily Visitors | 4 | -28.57% |
| Daily Visitors Rank | 24,653,967 | 2,373,555 |
| Daily Pageviews | 0 | -80.77% |
| Daily Pageviews Rank | 25,064,197 | 12,477,428 |
| Pageviews Per User | 1.00 | -75.00% |
Content
www.Drsinha.com
Category: 'Otorhinolaryngology/Clinics and Practitioners'
Age: It went live on February 5th 2000, making it over 18 years, 2 months old.
- Popular pages
- drsinha.com Pradeep K Sinha, MD, PhD, FACS Board Certified Otolaryngologis ..
- drsinha.com Ear Tubes Myringotomy and Tubes
- drsinha.com Sinusitis and Treatment
- drsinha.com Septoplasty, Nasal Septal Reconstruction
The estimated 5 daily visitors, each view 1 page on average.
Server| Server Location | |
| Web.com Inc. Georgia Atlanta United States 33.9348, -84.2703 | |
Its web server is located at Web.com Inc (Georgia, Atlanta.) Drsinha.com's server IP number is 66.223.124.241. a.ns.interland.net, b.ns.interland.net, and c.ns.interland.net are its DNS Nameservers.
IP: 66.223.124.241
| PING (66.223.124.241) 56(84) bytes of data. | |
| 64 bytes from freedommail.sinhafamily.com (66.223.124.241): icmp_seq=1 ttl=53 | 50.4 ms |
| 64 bytes from freedommail.sinhafamily.com (66.223.124.241): icmp_seq=2 ttl=53 | 48.7 ms |
| 64 bytes from freedommail.sinhafamily.com (66.223.124.241): icmp_seq=3 ttl=53 | 48.6 ms |
| --- ping statistics --- | |
| 3 packets transmitted, 3 received, 0% packet loss, time 2000ms | |
| rtt min/avg/max/mdev = 48.681/49.277/50.420/0.847 ms | |
| rtt min/avg/max/mdev = 48.681/49.277/50.420/0.847 ms |
Pinging the server, resulted in a 50.4 ms response.