Test Results for domain: box.pulptickets.com

Find IP Address - Results: 27 Apr 2024 10:08:40 PM

S. No.
Domain Name
IP Address
0
box.pulptickets.com
fire-aws-lb.totalticketing.d1.rbzdns.com./3.1.242.144
1
box.pulptickets.com
fire-aws-lb.totalticketing.d1.rbzdns.com./13.250.248.30

Check Website Availability - Results: 27 Apr 2024 10:10:43 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
Read timeout- Response wasn''t received within {0} seconds.
0
0
0
0
0 b
0
Nagano - JP
Read timeout- Response wasn''t received within {0} seconds.
0
0
0
0
0 b
0
Virginia - US
Read timeout- Response wasn''t received within {0} seconds.
0
0
0
0
0 b
0
Stockholm - SWE
Read timeout- Response wasn''t received within {0} seconds.
0
0
0
0
0 b
0

DNS Results: 27 Apr 2024 10:08:40 PM

DNS Results : box.pulptickets.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
3.1.242.144 ec2-3-1-242-144.ap-southeast-1.compute.amazonaws.com. 144.242.1.3.in-addr.arpa. OK
13.250.248.30 ec2-13-250-248-30.ap-southeast-1.compute.amazonaws.com. 30.248.250.13.in-addr.arpa. OK
Name Server Performance
Server Resolved IP TTL Response Time (ms) Status
ns77.domaincontrol.com.[97.74.108.49] box.pulptickets.com. ->fire-aws-lb.totalticketing.d1.rbzdns.com.(CNAME) 3600 27 OK
ns78.domaincontrol.com.[173.201.76.49] box.pulptickets.com. ->fire-aws-lb.totalticketing.d1.rbzdns.com.(CNAME) 3600 6 OK
Namespace Server delegation
Root Server Glue IP mapping Name Server mapping Status
Root Server Glue IP ns77.domaincontrol.com. 97.74.108.49 OK
ns78.domaincontrol.com. 173.201.76.49
97.74.108.49[ns77.domaincontrol.com.] - Possible DNS forwarding issue.
2603:5:22c4::31[ns78.domaincontrol.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] ns77.domaincontrol.com. 6 OK
ns78.domaincontrol.com.
b.gtld-servers.net.[192.33.14.30] ns77.domaincontrol.com. 22 OK
ns78.domaincontrol.com.
c.gtld-servers.net.[192.26.92.30] ns77.domaincontrol.com. 7 OK
ns78.domaincontrol.com.
d.gtld-servers.net.[192.31.80.30] ns77.domaincontrol.com. 6 OK
ns78.domaincontrol.com.
e.gtld-servers.net.[192.12.94.30] ns77.domaincontrol.com. 5 OK
ns78.domaincontrol.com.
f.gtld-servers.net.[192.35.51.30] ns77.domaincontrol.com. 33 OK
ns78.domaincontrol.com.
g.gtld-servers.net.[192.42.93.30] ns77.domaincontrol.com. 31 OK
ns78.domaincontrol.com.
h.gtld-servers.net.[192.54.112.30] ns77.domaincontrol.com. 32 OK
ns78.domaincontrol.com.
i.gtld-servers.net.[192.43.172.30] ns77.domaincontrol.com. 31 OK
ns78.domaincontrol.com.
j.gtld-servers.net.[192.48.79.30] ns77.domaincontrol.com. 28 OK
ns78.domaincontrol.com.
k.gtld-servers.net.[192.52.178.30] ns77.domaincontrol.com. 24 OK
ns78.domaincontrol.com.
l.gtld-servers.net.[192.41.162.30] ns77.domaincontrol.com. 28 OK
ns78.domaincontrol.com.
m.gtld-servers.net.[192.55.83.30] ns77.domaincontrol.com. 23 OK
ns78.domaincontrol.com.

Ping - Results: 27 Apr 2024 10:08:40 PM

Location
Status
IP
Packet Loss(ms)
Min RTT(ms)
Max RTT(ms)
Avg. RTT(ms)
Response Time(ms)

Ping - Results: 27 Apr 2024 10:08:40 PM

Location
Status
IP
Packet Loss(ms)
Min RTT(ms)
Max RTT(ms)
Avg. RTT(ms)
Response Time(ms)
Fremont-CA - US
13.250.248.30
100
0
0
0
0
Virginia - US
3.1.242.144
100
0
0
0
0
Nagano - JP
13.250.248.30
100
0
0
0
0
Stockholm - SWE
3.1.242.144
100
0
0
0
0
Fremont-CA - US
13.250.248.30
100
0
0
0
0
Virginia - US
13.250.248.30
100
0
0
0
0
Stockholm - SWE
3.1.242.144
100
0
0
0
0
Nagano - JP
13.250.248.30
100
0
0
0
0
Email Sign up and monitor your servers and apps now!

A service by Corp. © 2024. All Rights Reserved.