attackgoose.com - dns.ninja
attackgoose.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 38.6.230.195🇭🇰 AS39847838.6.224.0/19 PEG TECH INC | ||||||
| NS | ns1.julydns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns1.onclouddns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.onclouddns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1782902918 | ||||||
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=1783179481 | ||||||
Subdomains
ns1.attackgoose.com |
Same first word
attackgoose.com |
Similar names
DNS History
25 records (5 active, 20 former)
○NSdns1.registrar-servers.com2015-05-19 → 2018-06-15 · 7 obs
● 2015-12-21 12:59:34
○ 2016-03-31 06:42:12
○ 2016-12-15 14:46:40
● 2018-06-15 19:01:10
○ 2026-03-03 02:42:40
○ 2026-07-04 16:08:38
○NSdns1.registrar-servers.com,2016-03-31 → 2016-12-15 · 5 obs
● 2016-03-31 06:42:12
● 2016-12-15 14:46:40
○ 2018-06-15 19:01:10
○ 2026-07-04 16:08:38
○NSdns101.registrar-servers.com2026-04-10 → 2026-05-20 · 5 obs
● 2026-04-10 18:55:30
● 2026-05-20 02:38:38
○ 2026-05-23 03:00:48
○ 2026-07-04 16:08:38
○NSdns102.registrar-servers.com2026-04-10 → 2026-05-20 · 5 obs
● 2026-04-10 18:55:30
● 2026-05-20 02:38:38
○ 2026-05-23 03:00:48
○ 2026-07-04 16:08:38
○NSdns2.registrar-servers.com2015-05-19 → 2018-06-15 · 4 obs
● 2018-06-15 19:01:10
○ 2026-03-03 02:42:40
○ 2026-07-04 16:08:38
○NSdns3.registrar-servers.com2015-05-19 → 2016-12-15 · 4 obs
● 2016-12-15 14:46:40
○ 2018-06-15 19:01:10
○ 2026-07-04 16:08:38
○NSdns4.registrar-servers.com2015-05-19 → 2016-12-15 · 4 obs
● 2016-12-15 14:46:40
○ 2018-06-15 19:01:10
○ 2026-07-04 16:08:38
○NSdns5.registrar-servers.com2015-05-19 → 2016-12-15 · 4 obs
● 2016-12-15 14:46:40
○ 2018-06-15 19:01:10
○ 2026-07-04 16:08:38
○NSns1.afternic.com2026-03-03 → 2026-04-07 · 5 obs
● 2026-03-03 02:42:40
● 2026-04-07 11:50:08
○ 2026-04-10 18:55:30
○ 2026-07-04 16:08:38
●NSns1.julydns.com2026-07-01 → 2026-07-04 · 3 obs
● 2026-07-01 12:34:48
● 2026-07-04 16:08:38
●NSns1.onclouddns.com2026-07-01 → 2026-07-04 · 3 obs
● 2026-07-01 12:34:48
● 2026-07-04 16:08:38
○NSns2.afternic.com2026-03-03 → 2026-04-07 · 5 obs
● 2026-03-03 02:42:40
● 2026-04-07 11:50:08
○ 2026-04-10 18:55:30
○ 2026-07-04 16:08:38
●NSns2.julydns.com2026-07-01 → 2026-07-04 · 3 obs
● 2026-07-01 12:34:48
● 2026-07-04 16:08:38
●NSns2.onclouddns.com2026-07-01 → 2026-07-04 · 3 obs
● 2026-07-01 12:34:48
● 2026-07-04 16:08:38
○MXin1.smtp.messagingengine.com2015-05-19 → 2018-06-15 · 4 obs
● 2018-06-15 19:01:10
○ 2026-03-03 02:42:40
○ 2026-07-04 16:08:38
○MXmx.plingest.com2026-04-10 → 2026-05-20 · 5 obs
● 2026-04-10 18:55:30
● 2026-05-20 02:38:38
○ 2026-05-23 03:00:48
○ 2026-07-04 16:08:38
○A13.248.169.482026-03-03 → 2026-04-07 · 5 obs
● 2026-03-03 02:42:40
● 2026-04-07 11:50:08
○ 2026-04-10 18:55:30
○ 2026-07-04 16:08:38
○A162.255.119.2252018-06-15 → 2018-06-15 · 4 obs
● 2018-06-15 19:01:10
○ 2026-03-03 02:42:40
○ 2026-07-04 16:08:38
○A162.255.119.2512015-12-21 → 2015-12-21 · 4 obs
● 2015-12-21 12:59:34
○ 2016-03-31 06:42:12
○ 2026-07-04 16:08:38
○A172.234.24.2112026-04-10 → 2026-05-20 · 5 obs
● 2026-04-10 18:55:30
● 2026-05-20 02:38:38
○ 2026-05-23 03:00:48
○ 2026-07-04 16:08:38
○A172.239.57.1172026-04-10 → 2026-05-20 · 5 obs
● 2026-04-10 18:55:30
● 2026-05-20 02:38:38
○ 2026-05-23 03:00:48
○ 2026-07-04 16:08:38
○A192.64.119.2112016-03-31 → 2016-12-15 · 5 obs
● 2016-03-31 06:42:12
● 2016-12-15 14:46:40
○ 2018-06-15 19:01:10
○ 2026-07-04 16:08:38
●A38.6.230.1952026-07-01 → 2026-07-04 · 3 obs
● 2026-07-01 12:34:48
● 2026-07-04 16:08:38
○A68.65.123.2362015-05-19 → 2015-10-11 · 4 obs
● 2015-10-11 05:55:28
○ 2015-12-21 12:59:34
○ 2026-07-04 16:08:38
○A76.223.54.1462026-03-03 → 2026-04-07 · 5 obs
● 2026-03-03 02:42:40
● 2026-04-07 11:50:08
○ 2026-04-10 18:55:30
○ 2026-07-04 16:08:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| attackgoose.com | ns1.onclouddns.com, ns2.onclouddns.com | 2 records |
✅ Authoritative Response
Server:162.159.27.251
NS records: ns1.onclouddns.com, ns2.onclouddns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for attackgoose.com (unsigned zone)
⏱️ Timing
Total: 375ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 38.6.230.195 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.onclouddns.com, ns2.onclouddns.com)
Analysis
Hierarchy
attackgoose.com is the parent zone for ns1.attackgoose.com.
IP Addresses
attackgoose.com has exactly one IP address — 38.6.230.195.
x9258.com, jieyanbar.com, www.x9258.com plus two other host names have IP numbers in common with attackgoose.com.
Name Servers
Four name servers handle the delegation for attackgoose.com: ns1.julydns.com, ns2.julydns.com, ns1.onclouddns.com and ns2.onclouddns.com.
attackgoose.com partially shares its NS delegation with several other domains, including rgcd.cn, 815693.cn, izerodu.com and two others.
These name servers are regularly seen alongside ns1.judns.com and ns2.judns.com as name servers.
ns1.julydns.com and ns2.julydns.com share the IP address 162.159.48.223; ns1.onclouddns.com and ns2.onclouddns.com share the IP address 162.159.27.251.
The host names ns1.julydns.com and ns2.julydns.com both resolve to 162.159.48.223 IP addresses.
The host names ns1.onclouddns.com and ns2.onclouddns.com both resolve to 162.159.27.251 IP addresses.