Find IP Address - Results: 25 Apr 2024 09:53:58 PM
S. No.
Domain Name
IP Address
0
powerin.io
powerin.io./75.2.70.75
1
powerin.io
powerin.io./99.83.190.102
Ping - Results: 25 Apr 2024 09:53:58 PM
Location
Status
IP
Packet Loss(ms)
Min RTT(ms)
Max RTT(ms)
Avg. RTT(ms)
Response Time(ms)
Fremont-CA - US
75.2.70.75
0
1
1
1
1
Dallas - US
75.2.70.75
0
1
1
1
1
Amsterdam - NL
75.2.70.75
0
0
1
1
1
Johannesburg - ZA
75.2.70.75
0
1
1
1
1
DNS Results: 25 Apr 2024 09:53:58 PM
DNS Results : powerin.io
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
99.83.190.102
aacb0a264e514dd48.awsglobalaccelerator.com.
102.190.83.99.in-addr.arpa.
OK
75.2.70.75
aacb0a264e514dd48.awsglobalaccelerator.com.
75.70.2.75.in-addr.arpa.
OK
Name Server Performance
Server
Resolved IP
TTL
Response Time (ms)
Status
dns1.registrar-servers.com.[156.154.132.200]
75.2.70.75
1799
31
OK
dns2.registrar-servers.com.[156.154.133.200]
99.83.190.102
1799
23
OK
Namespace Server delegation
Root Server Glue IP mapping
Name Server mapping
Status
Root Server Glue IP
dns1.registrar-servers.com.
156.154.132.200
OK
dns2.registrar-servers.com.
156.154.133.200
156.154.132.200[dns1.registrar-servers.com.]
-
Possible DNS forwarding issue.
156.154.133.200[dns2.registrar-servers.com.]
-
Possible DNS forwarding issue.
DNS Traversal- performed using
m.root-servers.net.