abuser.com - dns.ninja
abuser.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | 45cfae0343489c1e92303bfeb1a75b1f7f7386cf | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1782927670 | ||||||
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=1786362829 | ||||||
Subdomains
www.abuser.com |
Same first word
Similar names
DNS History
10 records (4 active, 6 former)
○NSbuy.internettraffic.com2015-08-08 → 2016-06-22 · 4 obs
● 2016-06-22 23:56:52
○ 2017-02-06 09:37:46
○ 2026-08-10 12:22:24
●NSlaunch1.spaceship.net2026-03-03 → 2026-08-10 · 3 obs
● 2026-03-03 18:08:34
● 2026-08-10 12:22:24
●NSlaunch2.spaceship.net2026-03-03 → 2026-08-10 · 3 obs
● 2026-03-03 18:08:34
● 2026-08-10 12:22:24
○NSns1.uniregistrymarket.link2017-02-06 → 2017-02-06 · 4 obs
● 2017-02-06 09:37:46
○ 2026-03-03 18:08:34
○ 2026-08-10 12:22:24
○NSns2.uniregistrymarket.link2017-02-06 → 2017-02-06 · 4 obs
● 2017-02-06 09:37:46
○ 2026-03-03 18:08:34
○ 2026-08-10 12:22:24
○NSsell.internettraffic.com2015-08-08 → 2016-06-22 · 4 obs
● 2016-06-22 23:56:52
○ 2017-02-06 09:37:46
○ 2026-08-10 12:22:24
●A44.232.173.2492026-03-03 → 2026-08-10 · 3 obs
● 2026-03-03 18:08:34
● 2026-08-10 12:22:24
●A52.40.42.1132026-03-03 → 2026-08-10 · 3 obs
● 2026-03-03 18:08:34
● 2026-08-10 12:22:24
○A69.172.201.1532016-06-22 → 2017-02-06 · 5 obs
● 2016-06-22 23:56:52
● 2017-02-06 09:37:46
○ 2026-03-03 18:08:34
○ 2026-08-10 12:22:24
○A69.172.201.2082015-08-08 → 2016-03-05 · 4 obs
● 2016-03-05 01:09:50
○ 2016-06-22 23:56:52
○ 2026-08-10 12:22:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net... | - |
| abuser.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for abuser.com (unsigned zone)
⏱️ Timing
Total: 281ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 45cfae0343489c1e92303bfeb1a75b1f7f7386cf |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
Hierarchy
abuser.com is the parent zone for www.abuser.com.
IP Addresses
abuser.com directs to two IP numbers, 44.232.173.249 and 52.40.42.113
Among the host names that share IP numbers with abuser.com are qdsf.com, eehz.com, icanada.org and two others.
Name Servers
The NS records for abuser.com delegate to launch1.spaceship.net and launch2.spaceship.net.
abuser.com has the same name server delegation as a number of other domains, such as skycoworking.com, holdingbreath.com, toplent.com and two more.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.