Test Results for domain: cobratate.com

Check Website Availability - Results: 30 Apr 2024 03:51:13 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
104.18.9.153
13
2
16
92
48 KB
123
Virginia - US
OK
104.18.8.153
5
2
23
112
48 KB
142
Nagano - JP
OK
104.18.9.153
83
6
17
120
48 KB
226
Stockholm - SWE
OK
104.18.8.153
12
2
17
67
48 KB
98

Find Location - Results: 30 Apr 2024 03:48:35 PM

Location information: cobratate.com
Country Code
US
Country Name
UNITED STATES
Region
CALIFORNIA
City
SAN FRANCISCO

Find IP Address - Results: 30 Apr 2024 03:48:35 PM

S. No.
Domain Name
IP Address
0
cobratate.com
cobratate.com./104.18.9.153
1
cobratate.com
cobratate.com./104.18.8.153

Ping - Results: 30 Apr 2024 03:48:35 PM

Location
Status
IP
Packet Loss(ms)
Min RTT(ms)
Max RTT(ms)
Avg. RTT(ms)
Response Time(ms)
Fremont-CA - US
104.18.8.153
0
2
2
2
1
Dallas - US
104.18.9.153
0
2
2
2
1
Amsterdam - NL
104.18.8.153
0
1
1
1
1
Johannesburg - ZA
104.18.8.153
0
0
0
0
1

DNS Results: 30 Apr 2024 03:48:35 PM

DNS Results : cobratate.com
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
104.18.9.153 OK
104.18.8.153 OK
Name Server Performance
Server Resolved IP TTL Response Time (ms) Status
bob.ns.cloudflare.com.[108.162.193.104] 104.18.9.153 300 17 OK
heidi.ns.cloudflare.com.[108.162.194.236] 104.18.8.153 300 7 OK
Namespace Server delegation
Root Server Glue IP mapping Name Server mapping Status
Root Server Glue IP bob.ns.cloudflare.com. 108.162.193.104 OK
heidi.ns.cloudflare.com. 108.162.194.236
2a06:98c1:50::ac40:2168[bob.ns.cloudflare.com.] - Possible DNS forwarding issue.
2a06:98c1:50::ac40:22ec[heidi.ns.cloudflare.com.] - Possible DNS forwarding issue.
DNS Traversal- performed using h.root-servers.net.
Server Name Servers Response Time (ms) Status
a.gtld-servers.net.[192.5.6.30] bob.ns.cloudflare.com. 6 OK
heidi.ns.cloudflare.com.
b.gtld-servers.net.[192.33.14.30] bob.ns.cloudflare.com. 24 OK
heidi.ns.cloudflare.com.
c.gtld-servers.net.[192.26.92.30] bob.ns.cloudflare.com. 4 OK
heidi.ns.cloudflare.com.
d.gtld-servers.net.[192.31.80.30] bob.ns.cloudflare.com. 7 OK
heidi.ns.cloudflare.com.
e.gtld-servers.net.[192.12.94.30] bob.ns.cloudflare.com. 4 OK
heidi.ns.cloudflare.com.
f.gtld-servers.net.[192.35.51.30] bob.ns.cloudflare.com. 31 OK
heidi.ns.cloudflare.com.
g.gtld-servers.net.[192.42.93.30] bob.ns.cloudflare.com. 23 OK
heidi.ns.cloudflare.com.
h.gtld-servers.net.[192.54.112.30] bob.ns.cloudflare.com. 30 OK
heidi.ns.cloudflare.com.
i.gtld-servers.net.[192.43.172.30] bob.ns.cloudflare.com. 31 OK
heidi.ns.cloudflare.com.
j.gtld-servers.net.[192.48.79.30] bob.ns.cloudflare.com. 30 OK
heidi.ns.cloudflare.com.
k.gtld-servers.net.[192.52.178.30] bob.ns.cloudflare.com. 23 OK
heidi.ns.cloudflare.com.
l.gtld-servers.net.[192.41.162.30] bob.ns.cloudflare.com. 28 OK
heidi.ns.cloudflare.com.
m.gtld-servers.net.[192.55.83.30] bob.ns.cloudflare.com. 23 OK
heidi.ns.cloudflare.com.