ping-api.com - dns.ninja
ping-api.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1782455965 | ||||||
Same first word
ping-api.com |
DNS History
6 records (6 active, 0 former)
●NSns-1147.awsdns-15.org2016-12-20 → 2026-06-26 · 2 obs
● 2026-06-26 06:42:24
●NSns-1602.awsdns-08.co.uk2016-12-20 → 2026-06-26 · 2 obs
● 2026-06-26 06:42:24
●NSns-17.awsdns-02.com2016-12-20 → 2026-06-26 · 2 obs
● 2026-06-26 06:42:24
●NSns-517.awsdns-00.net2016-12-20 → 2026-06-26 · 2 obs
● 2026-06-26 06:42:24
●MXinbound-smtp.us-west-2.amazonaws.com2016-12-20 → 2026-06-26 · 2 obs
● 2026-06-26 06:42:24
●A52.34.133.42016-12-20 → 2026-06-26 · 2 obs
● 2026-06-26 06:42:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ping-api.com | ns-17.awsdns-02.com, ns-517.awsdns-00.net, ns-1602.awsdns-08.co.uk, ns-1147.awsdns-15.org | 2 records |
✅ Authoritative Response
Server:205.251.198.66
NS records: ns-17.awsdns-02.com, ns-517.awsdns-00.net, ns-1602.awsdns-08.co.uk, ns-1147.awsdns-15.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ping-api.com (unsigned zone)
⏱️ Timing
Total: 468ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.34.133.4 |
| NS | 4 | ns-1147.awsdns-15.org, ns-1602.awsdns-08.co.uk... |
| MX | 1 | inbound-smtp.us-west-2.amazonaws.com (pr |
| SOA | 1 | ns-1147.awsdns-15.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-17.awsdns-02.com, ns-17.awsdns-02.com)
Analysis
IP Addresses
ping-api.com has exactly one IP address — 52.34.133.4.
phate.org and ec2-52-34-133-4.us-west-2.compute.amazonaws.com, along with other host names, share IP addresses with ping-api.com.
Name Servers
Four name servers handle the delegation for ping-api.com: ns-17.awsdns-02.com, ns-517.awsdns-00.net, ns-1147.awsdns-15.org and ns-1602.awsdns-08.co.uk.
ping-api.com partially shares its NS delegation with several other domains, including d3d9mb8xdsbq52.cloudfront.net, d3jbwsr4pboqj.cloudfront.net, bidr.co and two others.
These name servers regularly co-occur with the name servers ns-796.awsdns-35.net, ns-1454.awsdns-53.org and ns-1751.awsdns-26.co.uk.
ns-17.awsdns-02.com, ns-517.awsdns-00.net, ns-1147.awsdns-15.org and ns-1602.awsdns-08.co.uk each carry two IP addresses. ns-17.awsdns-02.com has 205.251.192.17 and 2600:9000:5300:1100::1; ns-517.awsdns-00.net has 205.251.194.5 and 2600:9000:5302:500::1; ns-1147.awsdns-15.org has 205.251.196.123 and 2600:9000:5304:7b00::1; ns-1602.awsdns-08.co.uk has 205.251.198.66 and 2600:9000:5306:4200::1.
Mail Servers
ping-api.com uses one mail server — inbound-smtp.us-west-2.amazonaws.com.
The mail server setup of ping-api.com matches that of other domains such as cloudrcs.net, public.jupiter-radio.net, meibamen.com and two others.
At least some of the mail servers used by ping-api.com are shared with other domains: anritsu-m1tg.atlassian.net, soc-safeway.atlassian.net, uniteus.atlassian.net and two others among them.
These mail servers are often deployed together with inbound-smtp.us-east-1.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other mail servers.
inbound-smtp.us-west-2.amazonaws.com points to four IP addresses: 35.161.157.106, 52.13.163.116, 52.43.162.244 and 54.188.121.70.