Test Results for domain: www.collibetindia.in

Find IP Address - Results: 04 Mar 2024 08:04:56 PM

S. No.
Domain Name
IP Address
0
www.collibetindia.in
www.collibetindia.in./172.67.179.100
1
www.collibetindia.in
www.collibetindia.in./104.21.88.131

Ping - Results: 04 Mar 2024 08:04:56 PM

Location
Status
IP
Packet Loss(ms)
Min RTT(ms)
Max RTT(ms)
Avg. RTT(ms)
Response Time(ms)
Fremont-CA - US
104.21.88.131
0
1
1
1
1
Dallas - US
172.67.179.100
0
2
2
2
1
Amsterdam - NL
188.114.96.0
0
1
1
1
1
Johannesburg - ZA
104.21.88.131
0
148
148
148
147

Check Website Availability - Results: 04 Mar 2024 08:05:30 PM

DNS
Time taken for the server to resolve DNS name to IP Address
Connect
Time taken to setup the between connection Site24x7 and website
First Byte
The time spent waiting for the web server to send data.
Last Byte
The time at which the entire content of the file is downloaded
Location
Status
IP
(ms)
(ms)
(ms)
(ms)
Size
Response
Time (ms)
Fremont-CA - US
OK
172.67.179.100
8
2
30
1,304
75 KB
1,344
Virginia - US
OK
172.67.179.100
7
1
13
1,075
75 KB
1,096
Nagano - JP
OK
172.67.179.100
28
8
34
759
75 KB
829
Stockholm - SWE
OK
188.114.96.1
42
10
20
1,023
75 KB
1,095

Find Location - Results: 04 Mar 2024 08:04:56 PM

Location information: www.collibetindia.in
Country Code
US
Country Name
UNITED STATES
Region
CALIFORNIA
City
SAN FRANCISCO

DNS Results: 04 Mar 2024 08:04:56 PM

DNS Results : www.collibetindia.in
SOA Record(s)
Field Value
No Record(s) Found
The SOA record for the zone is required to be present in the primary Name Server and is not found. This usually means that the zone file is not setup properly in the primary Name Server host. It may also be due to any of the following reasons.
The Name Server domain is actually not running at all. Start your Name Server domain before running this test again.
The Name Server domain is not reachable from the Internet because there is a firewall or filtering router that is blocking connections to port 53 on this host for both UDP and TCP connections. The firewall configuration must permit connections on this port from any host on the Internet for the DNS to function properly.
MX Record(s)
Target IP Priority TTL
No Record(s) Found
Reverse Lookup
IP Address Reverse Lookup Name Reverse IP Address Status
172.67.179.100 OK
104.21.88.131 OK
Name Server Performance
Server Resolved IP TTL Response Time (ms) Status
bingo.ns.cloudflare.com.[172.64.34.36] 172.67.179.100 300 39 OK
yichun.ns.cloudflare.com.[172.64.33.248] 104.21.88.131 300 19 OK
Namespace Server delegation
Root Server Glue IP mapping Name Server mapping Status
Root Server Glue IP bingo.ns.cloudflare.com. 172.64.34.36 OK
yichun.ns.cloudflare.com. 172.64.33.248
172.64.34.36[bingo.ns.cloudflare.com.] - Possible DNS forwarding issue.
172.64.33.248[yichun.ns.cloudflare.com.] - Possible DNS forwarding issue.
DNS Traversal- performed using d.root-servers.net.
Server Name Servers Response Time (ms) Status
ns1.registry.in.[37.209.192.12] bingo.ns.cloudflare.com. 6 OK
yichun.ns.cloudflare.com.
ns2.registry.in.[37.209.194.12] yichun.ns.cloudflare.com. 6 OK
bingo.ns.cloudflare.com.
ns3.registry.in.[37.209.196.12] bingo.ns.cloudflare.com. 30 OK
yichun.ns.cloudflare.com.
ns4.registry.in.[37.209.198.12] bingo.ns.cloudflare.com. 7 OK
yichun.ns.cloudflare.com.
ns5.registry.in.[156.154.100.20] yichun.ns.cloudflare.com. 21 OK
bingo.ns.cloudflare.com.
ns6.registry.in.[156.154.101.20] bingo.ns.cloudflare.com. 7 OK
yichun.ns.cloudflare.com.