attack-killer.com - dns.ninja

`attack-killer.com`

DNSSEC	⚠️ Not signed
A	193.24.127.108^{GTT-BACKBONE193.24.127.0/24}
NS	`ns-1911.awsdns-46.co.uk` ⭐ ⚠️ Not in parent delegation
		A	2600:9000:5307:7700::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1911.awsdns-46.co.uk`
		A	205.251.199.119^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1911.awsdns-46.co.uk`
NS	`ns-1210.awsdns-23.org` ⚠️ Not in parent delegation
		A	2600:9000:5304:ba00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1210.awsdns-23.org`
		A	205.251.196.186^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1210.awsdns-23.org`
NS	`ns-1243.awsdns-27.org` ⚠️ Not in parent delegation
		A	2600:9000:5304:db00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1243.awsdns-27.org`
		A	205.251.196.219^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1243.awsdns-27.org`
NS	`ns-146.awsdns-18.com` ⚠️ Not in parent delegation
		A	2600:9000:5300:9200::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-146.awsdns-18.com`
		A	205.251.192.146^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-146.awsdns-18.com`
NS	`ns1.attack-killer.com` ⚠️ Not in zone NS records
NS	`ns2.attack-killer.com` ⚠️ Not in zone NS records
MX	`mx.attack-killer.com` ⭐
		A	193.24.127.108^{GTT-BACKBONE193.24.127.0/24}
TXT	`v=spf1 include:thinkaheadconsultants.com include:buttuglycup.com -all`
SOA	`ns-1911.awsdns-46.co.uk`awsdns-hostmaster@amazon.com serial=1

`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.net`nstld@verisign-grs.com serial=1782610805

Subdomains

ns1.attack-killer.com

mx.attack-killer.com

ns2.attack-killer.com

Same first word

attack-killer.com

DNS History

13 records (8 active, 5 former)

●NSns-1210.awsdns-23.org2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

●NSns-1243.awsdns-27.org2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

●NSns-146.awsdns-18.com2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

●NSns-1911.awsdns-46.co.uk2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

●NSns1.attack-killer.com2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

○NSns1.digitalocean.com2017-08-31 → 2017-08-31 · 3 obs

● 2017-08-31 23:46:26
○ 2026-03-22 07:22:10
○ 2026-06-28 01:40:48

●NSns2.attack-killer.com2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

○NSns2.digitalocean.com2017-08-31 → 2017-08-31 · 3 obs

● 2017-08-31 23:46:26
○ 2026-03-22 07:22:10
○ 2026-06-28 01:40:48

○NSns3.digitalocean.com2017-08-31 → 2017-08-31 · 3 obs

● 2017-08-31 23:46:26
○ 2026-03-22 07:22:10
○ 2026-06-28 01:40:48

●MXmx.attack-killer.com2026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

○MXmx.yandex.net2017-08-31 → 2017-08-31 · 3 obs

● 2017-08-31 23:46:26
○ 2026-03-22 07:22:10
○ 2026-06-28 01:40:48

○A188.226.180.842017-08-31 → 2017-08-31 · 3 obs

● 2017-08-31 23:46:26
○ 2026-03-22 07:22:10
○ 2026-06-28 01:40:48

●A193.24.127.1082026-03-22 → 2026-06-28 · 3 obs

○ 2017-08-31 23:46:26
● 2026-03-22 07:22:10
● 2026-06-28 01:40:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
attack-killer.com	ns1.attack-killer.com, ns2.attack-killer.com	2 records

✅ Authoritative Response

Server:51.38.212.252

NS records: ns1.attack-killer.com, ns2.attack-killer.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for attack-killer.com (unsigned zone)

⏱️ Timing

Total: 570ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`193.24.127.108`
NS	4	`ns-146.awsdns-18.com, ns-1911.awsdns-46.co.uk...`
MX	1	`mx.attack-killer.com (pri: 0)`
TXT	1	`v=spf1 include:thinkaheadconsultants.com`
SOA	1	`ns-1911.awsdns-46.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.attack-killer.com, ns2.attack-killer.com)

Analysis

Hierarchy

attack-killer.com is the parent domain of ns1.attack-killer.com, mx.attack-killer.com and ns2.attack-killer.com.

IP Addresses

attack-killer.com resolves to one IP address: 193.24.127.108.

Other host names share IP numbers with attack-killer.com; mx.attack-killer.com is one such example.

Name Servers

The DNS delegation for attack-killer.com covers 6 name servers: ns1.attack-killer.com, ns2.attack-killer.com, ns-146.awsdns-18.com and 3 more.

attack-killer.com shares at least some of its name servers with other domains, including patrickturley.com, hayamax.com.br, tarrison.com and two others.

These name servers are frequently paired with the name servers ns-1210.awsdns-23.org, ns-1243.awsdns-27.org and ns-1911.awsdns-46.co.uk.

The host names ns-146.awsdns-18.com, ns-1210.awsdns-23.org, ns-1243.awsdns-27.org and ns-1911.awsdns-46.co.uk each resolve to two IP addresses: ns-146.awsdns-18.com resolves to 205.251.192.146 and 2600:9000:5300:9200::1; ns-1210.awsdns-23.org resolves to 205.251.196.186 and 2600:9000:5304:ba00::1; ns-1243.awsdns-27.org resolves to 205.251.196.219 and 2600:9000:5304:db00::1; ns-1911.awsdns-46.co.uk resolves to 205.251.199.119 and 2600:9000:5307:7700::1.

Mail Servers

Mail for attack-killer.com is handled by a single mail server, mx.attack-killer.com.

There is one IP number for mx.attack-killer.com: 193.24.127.108.