Satennisopen.co.za
Satennisopen is ranked > 3,000,000 in the United Kingdom. 'SA Tennis Open - Montecasino Johannesburg 31 Jan - 6 Feb 2011.'
--Rank in United Kingdom
--Worldwide Rank
| Monthly pages viewed | < 300 | |
| Monthly visits | < 300 | |
| Value per visitor | -- | |
| Estimated worth | £376.42 | |
| External links | 76 | |
| Number of pages | 225 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Content
www.Satennisopen.co.za
- Popular pages
- satennisopen.co.za SA TENNIS OPEN 2011 - OFFICIAL MAIN DRAW
- satennisopen.co.za LIVE DRAW AND FREE TENNIS AT SA OPEN QUALIFYING TOURNAMENT
- satennisopen.co.za Draws & Order of Play
- satennisopen.co.za TOP OFFICIALS FOR SA TENNIS OPEN AT MONTECASINO
- Links in
- globalbuzz.net GlobalBuzz — All the News from Around the Globe
- tennisbetting365.com Tennis Betting Predictions, Betting Tips and Advice - Home
- Links out
- joomlaworks.gr JoomlaWorks | Developers of popular Joomla! extensions like K2
- atpworldtour.com Tennis - ATP World Tour - Headline News
- atpworldtour.com Tennis - ATP World Tour - Tennis Players – Jo-Wilfried Tsonga
- montecasino.co.za Montecasino - Gauteng's Premier Entertainment Destination
| Server Location | |
| Slicehost Llc Missouri Laclede United States 39.7757, -93.1773 | |
The server is hosted by Slicehost Llc (Missouri, Laclede.) Satennisopen.co.za's server IP number is 67.23.27.61. ns02.webafrica.co.za, and ns01.webafrica.co.za are its DNS Nameservers.
IP: 67.23.27.61
| PING www. (67.23.27.61) 56(84) bytes of data. | |
| 64 bytes from 67-23-27-61.static.cloud-ips.com (67.23.27.61): icmp_seq=1 ttl=55 | 43.7 ms |
| 64 bytes from 67-23-27-61.static.cloud-ips.com (67.23.27.61): icmp_seq=2 ttl=55 | 34.7 ms |
| 64 bytes from 67-23-27-61.static.cloud-ips.com (67.23.27.61): icmp_seq=3 ttl=55 | 34.7 ms |
| --- www. ping statistics --- | |
| 3 packets transmitted, 3 received, 0% packet loss, time 1998ms | |
| rtt min/avg/max/mdev = 34.732/37.741/43.718/4.231 ms | |
| rtt min/avg/max/mdev = 34.732/37.741/43.718/4.231 ms |
Pinging the server, resulted in a 43.7 ms response.