rushname.com - dns.ninja
rushname.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.atom.com ⚠️ Not in zone NS records | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com ⚠️ Not in zone NS records | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| NS | verification-8uneycqadhrltns2lewzss.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.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=1784870092 | ||||||
Same first word
rushname.com |
Similar names
DNS History
7 records (3 active, 4 former)
●NSns1.atom.com2026-02-28 → 2026-07-24 · 3 obs
○ 2017-06-19 04:23:28
● 2026-02-28 01:49:30
● 2026-07-24 05:40:40
● 2026-02-28 01:49:30
● 2026-07-24 05:40:40
○NSns1.uniregistrymarket.link2016-09-17 → 2017-06-19 · 4 obs
● 2016-09-17 02:01:04
● 2017-06-19 04:23:28
○ 2026-02-28 01:49:30
○ 2026-07-24 05:40:40
● 2017-06-19 04:23:28
○ 2026-02-28 01:49:30
○ 2026-07-24 05:40:40
●NSns2.atom.com2026-02-28 → 2026-07-24 · 3 obs
○ 2017-06-19 04:23:28
● 2026-02-28 01:49:30
● 2026-07-24 05:40:40
● 2026-02-28 01:49:30
● 2026-07-24 05:40:40
○NSns2.uniregistrymarket.link2016-09-17 → 2017-06-19 · 4 obs
● 2016-09-17 02:01:04
● 2017-06-19 04:23:28
○ 2026-02-28 01:49:30
○ 2026-07-24 05:40:40
● 2017-06-19 04:23:28
○ 2026-02-28 01:49:30
○ 2026-07-24 05:40:40
●NSverification-8uneycqadhrltns2lewzss.ns101.verify.hn2026-02-28 → 2026-07-24 · 3 obs
○ 2017-06-19 04:23:28
● 2026-02-28 01:49:30
● 2026-07-24 05:40:40
● 2026-02-28 01:49:30
● 2026-07-24 05:40:40
○A52.20.84.622026-02-28 → 2026-02-28 · 4 obs
○ 2017-06-19 04:23:28
● 2026-02-28 01:49:30
○ 2026-06-13 06:26:24
○ 2026-07-24 05:40:40
● 2026-02-28 01:49:30
○ 2026-06-13 06:26:24
○ 2026-07-24 05:40:40
○A69.172.201.1532016-09-17 → 2017-06-19 · 4 obs
● 2016-09-17 02:01:04
● 2017-06-19 04:23:28
○ 2026-02-28 01:49:30
○ 2026-07-24 05:40:40
● 2017-06-19 04:23:28
○ 2026-02-28 01:49:30
○ 2026-07-24 05:40:40
🔍 DNS Trace
Analysis
Name Servers
rushname.com has three name servers — ns1.atom.com, ns2.atom.com and verification-8uneycqadhrltns2lewzss.ns101.verify.hn.
rushname.com has at least partial name server overlap with other domains, such as (0x736578)ystrippers.com, indianfolkart.com, tirras.com and two others.
These name servers tend to appear together with the name servers ns1.afternic.com, ns2.afternic.com and verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.
Host names pointing to two IP addresses:
verification-8uneycqadhrltns2lewzss.ns101.verify.hn resolves to 13.248.169.48 and 76.223.54.146.
Host names resolving to a single IP address:
ns1.atom.com resolves to 44.219.81.145.
ns2.atom.com resolves to 50.19.240.86.