securerespond.com - dns.ninja
securerespond.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-1021.awsdns-63.net ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5303:fd00::1🇺🇸 Amazon2600:9000:5303::/48 - CloudFront | ||||||
| PTR | ns-1021.awsdns-63.net | ||||||
| A | 205.251.195.253🇺🇸 Amazon205.251.195.0/24 prefix | ||||||
| PTR | ns-1021.awsdns-63.net | ||||||
| NS | ns-1037.awsdns-01.org ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5304:d00::1🇺🇸 Amazon2600:9000:5304::/48 - CloudFront | ||||||
| PTR | ns-1037.awsdns-01.org | ||||||
| A | 205.251.196.13🇺🇸 Amazon205.251.196.0/24 prefix | ||||||
| PTR | ns-1037.awsdns-01.org | ||||||
| NS | ns-224.awsdns-28.com ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5300:e000::1🇺🇸 Amazon2600:9000:5300::/48 - CloudFront | ||||||
| PTR | ns-224.awsdns-28.com | ||||||
| A | 205.251.192.224🇺🇸 Amazon205.251.192.0/24 prefix | ||||||
| PTR | ns-224.awsdns-28.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=1785867024 | ||||||
Same first word
securerespond.com |
Similar names
DNS History
13 records (3 active, 10 former)
●NSns-1021.awsdns-63.net2026-03-12 → 2026-08-04 · 3 obs
● 2026-03-12 11:44:32
● 2026-08-04 18:33:24
●NSns-1037.awsdns-01.org2026-03-12 → 2026-08-04 · 3 obs
● 2026-03-12 11:44:32
● 2026-08-04 18:33:24
●NSns-224.awsdns-28.com2026-03-12 → 2026-08-04 · 3 obs
● 2026-03-12 11:44:32
● 2026-08-04 18:33:24
○NSns1.lnhi.net2008-03-15 → 2008-03-15 · 3 obs
○ 2015-10-16 22:40:42
○ 2026-08-04 18:33:24
○NSns2.lnhi.net2008-03-15 → 2008-03-15 · 3 obs
○ 2015-10-16 22:40:42
○ 2026-08-04 18:33:24
○NSns3.lnhi.net2008-03-15 → 2008-03-15 · 3 obs
○ 2015-10-16 22:40:42
○ 2026-08-04 18:33:24
○NSns7.rookdns.com2016-02-05 → 2016-07-09 · 5 obs
● 2016-02-05 04:58:28
● 2016-07-09 12:46:38
○ 2026-03-12 11:44:32
○ 2026-08-04 18:33:24
○NSns8.rookdns.com2016-02-05 → 2016-07-09 · 5 obs
● 2016-02-05 04:58:28
● 2016-07-09 12:46:38
○ 2026-03-12 11:44:32
○ 2026-08-04 18:33:24
○MXmail.mxproc.com2016-02-05 → 2016-04-25 · 5 obs
● 2016-02-05 04:58:28
● 2016-04-25 00:38:46
○ 2016-07-09 12:46:38
○ 2026-08-04 18:33:24
○MXmail.replyingback.com2016-07-09 → 2016-07-09 · 4 obs
● 2016-07-09 12:46:38
○ 2026-03-12 11:44:32
○ 2026-08-04 18:33:24
○MXmail.securerespond.com2008-03-15 → 2008-03-15 · 3 obs
○ 2015-10-16 22:40:42
○ 2026-08-04 18:33:24
○A141.8.224.932016-02-05 → 2016-07-09 · 5 obs
● 2016-02-05 04:58:28
● 2016-07-09 12:46:38
○ 2026-03-12 11:44:32
○ 2026-08-04 18:33:24
○A65.36.248.1502008-03-15 → 2008-03-15 · 3 obs
○ 2015-10-16 22:40:42
○ 2026-08-04 18:33:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net... | - |
| securerespond.com | ns-224.awsdns-28.com, ns-1021.awsdns-63.net, ns-1037.awsdns-01.org | 2 records |
✅ Authoritative Response
Server:205.251.192.224
NS records: ns-224.awsdns-28.com, ns-1021.awsdns-63.net, ns-1037.awsdns-01.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securerespond.com (unsigned zone)
⏱️ Timing
Total: 192ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-224.awsdns-28.com, ns-224.awsdns-28.com)
Analysis
Name Servers
securerespond.com has three name servers — ns-224.awsdns-28.com, ns-1021.awsdns-63.net and ns-1037.awsdns-01.org.
securerespond.com partially shares its NS delegation with several other domains, including mybank.sucks, vyntelligence.com, collaboplaza.com and two others.
Each of ns-224.awsdns-28.com, ns-1021.awsdns-63.net and ns-1037.awsdns-01.org points to two IP numbers. ns-224.awsdns-28.com points to 205.251.192.224 and 2600:9000:5300:e000::1. ns-1021.awsdns-63.net points to 205.251.195.253 and 2600:9000:5303:fd00::1. ns-1037.awsdns-01.org points to 205.251.196.13 and 2600:9000:5304:d00::1.