pushbot.io - dns.ninja
pushbot.io
io
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.io ⭐ | ||||||
| NS | a2.nic.io | ||||||
| NS | b0.nic.io | ||||||
| NS | c0.nic.io | ||||||
| SOA | a0.nic.iohostmaster@donuts.email serial=1785917389 | ||||||
Subdomains
assets.pushbot.io |
community-staging-site.pushbot.io |
Same first word
Similar names
DNS History
5 records (5 active, 0 former)
●NSns-1506.awsdns-60.org2017-05-24 → 2026-08-05 · 2 obs
● 2026-08-05 09:19:44
●NSns-1872.awsdns-42.co.uk2017-05-24 → 2026-08-05 · 2 obs
● 2026-08-05 09:19:44
●NSns-471.awsdns-58.com2017-05-24 → 2026-08-05 · 2 obs
● 2026-08-05 09:19:44
●NSns-988.awsdns-59.net2017-05-24 → 2026-08-05 · 2 obs
● 2026-08-05 09:19:44
●MXinbound-smtp.us-east-1.amazonaws.com2017-05-24 → 2026-08-05 · 2 obs
● 2026-08-05 09:19:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | c0.nic.io, a2.nic.io, a0.nic.io, b0.nic.io | - |
| pushbot.io | ns-1872.awsdns-42.co.uk, ns-471.awsdns-58.com, ns-988.awsdns-59.net, ns-1506.awsdns-60.org | - |
✅ Authoritative Response
Server:205.251.199.80
NS records: ns-1872.awsdns-42.co.uk, ns-471.awsdns-58.com, ns-988.awsdns-59.net, ns-1506.awsdns-60.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pushbot.io (unsigned zone)
⏱️ Timing
Total: 542ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1506.awsdns-60.org, ns-1872.awsdns-42.co.uk... |
| MX | 1 | inbound-smtp.us-east-1.amazonaws.com (pr |
| TXT | 1 | google-site-verification=-NMxvcgRHiz0Bhm |
| SOA | 1 | ns-988.awsdns-59.net awsdns-hostmaster.a |
Analysis
Hierarchy
The parent domain of assets.pushbot.io and community-staging-site.pushbot.io is pushbot.io.
Name Servers
The domain pushbot.io is delegated to these four name servers: ns-471.awsdns-58.com, ns-988.awsdns-59.net, ns-1506.awsdns-60.org and ns-1872.awsdns-42.co.uk.
pushbot.io has at least partial name server overlap with other domains, such as d13vod43o2zveb.cloudfront.net, otyehel.com, podcarcity.org and two others.
It is common to find these name servers paired with the name servers ns1-24-ap-northeast-1.ec2-rdns.amazonaws.com, ns2-24-ap-northeast-1.ec2-rdns.amazonaws.com, ns3-24-ap-northeast-1.ec2-rdns.amazonaws.com and ns4-24-ap-northeast-1.ec2-rdns.amazonaws.com.
ns-471.awsdns-58.com, ns-988.awsdns-59.net, ns-1506.awsdns-60.org and ns-1872.awsdns-42.co.uk all point to exactly two IP numbers each: ns-471.awsdns-58.com → 205.251.193.215 and 2600:9000:5301:d700::1; ns-988.awsdns-59.net → 205.251.195.220 and 2600:9000:5303:dc00::1; ns-1506.awsdns-60.org → 205.251.197.226 and 2600:9000:5305:e200::1; ns-1872.awsdns-42.co.uk → 205.251.199.80 and 2600:9000:5307:5000::1.
Mail Servers
pushbot.io routes its mail through a single mail server, inbound-smtp.us-east-1.amazonaws.com.
pushbot.io has the same mail server arrangement as a number of other domains, for example bdjw.ai, wecops.slack.com, central.pt.teramoba2.com and two more.
pushbot.io shares at least some of its mail servers with other domains — for example olympics.atlassian.net, harness.atlassian.net, civicert.atlassian.net and two more.
It is common to find these mail servers paired with the mail servers inbound-smtp.us-west-2.amazonaws.com.
inbound-smtp.us-east-1.amazonaws.com has five IP addresses: 3.211.210.226, 44.206.9.87, 44.210.166.32 plus two others.