sdslacker.com - dns.ninja

`sdslacker.com`

DNSSEC	⚠️ Not signed
NS	`ns01.slacker.com` ⭐
		A	204.239.14.11^{🇺🇸 AS32562204.239.14.0/24 SD}
			PTR	`ns01.slacker.com`
NS	`ns02.slacker.com`
		A	204.239.14.12^{🇺🇸 AS32562204.239.14.0/24 SD}
			PTR	`ns02.slacker.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c2d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ry-in-f27.1e100.net`
		A	142.250.31.26^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 a:relay01.slacker.com a:relay02.slacker.com ~all`
TXT	`google-site-verification=wKCSMRvpTtdWRyUWOH7IFlGh5b45TEbren3TCzr-AzQ`
SOA	`ns01.slacker.com`hostmaster@slacker.com 2017-03-25 #17

`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=1785114562

Subdomains

dev.sdslacker.com

stg.sdslacker.com

pubstg.sdslacker.com

Same first word

sdslacker.com

Similar names

redslacks.com

DNS History

9 records (7 active, 2 former)

●NSns01.slacker.com2015-07-17 → 2026-07-27 · 2 obs

● 2015-07-17 15:14:42
● 2026-07-27 01:29:38

●NSns02.slacker.com2015-07-17 → 2026-07-27 · 2 obs

● 2015-07-17 15:14:42
● 2026-07-27 01:29:38

●MXalt1.aspmx.l.google.com2026-03-23 → 2026-07-27 · 3 obs

○ 2017-12-06 21:12:04
● 2026-03-23 15:11:12
● 2026-07-27 01:29:38

●MXalt2.aspmx.l.google.com2026-03-23 → 2026-07-27 · 3 obs

○ 2017-12-06 21:12:04
● 2026-03-23 15:11:12
● 2026-07-27 01:29:38

●MXalt3.aspmx.l.google.com2026-03-23 → 2026-07-27 · 3 obs

○ 2017-12-06 21:12:04
● 2026-03-23 15:11:12
● 2026-07-27 01:29:38

●MXalt4.aspmx.l.google.com2026-03-23 → 2026-07-27 · 3 obs

○ 2017-12-06 21:12:04
● 2026-03-23 15:11:12
● 2026-07-27 01:29:38

●MXaspmx.l.google.com2026-03-23 → 2026-07-27 · 3 obs

○ 2017-12-06 21:12:04
● 2026-03-23 15:11:12
● 2026-07-27 01:29:38

○MXrelay01.slacker.com2015-07-17 → 2017-12-06 · 4 obs

● 2015-07-17 15:14:42
● 2017-12-06 21:12:04
○ 2026-03-23 15:11:12
○ 2026-07-27 01:29:38

○MXrelay02.slacker.com2015-07-17 → 2017-12-06 · 4 obs

● 2015-07-17 15:14:42
● 2017-12-06 21:12:04
○ 2026-03-23 15:11:12
○ 2026-07-27 01:29: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...	-
sdslacker.com	ns01.slacker.com, ns02.slacker.com	2 records

✅ Authoritative Response

Server:204.239.14.11

NS records: ns01.slacker.com, ns02.slacker.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sdslacker.com (unsigned zone)

⏱️ Timing

Total: 326ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns02.slacker.com, ns01.slacker.com`
MX	5	`ALT4.ASPMX.L.GOOGLE.COM (pri: 10), ALT1.ASPMX.L.GOOGLE.COM (pri: 5)...`
TXT	2	`google-site-verification=wKCSMRvpTtdWRyU, v=spf1 a:relay01.slacker.com a:relay02.s`
SOA	1	`ns01.slacker.com hostmaster.slacker.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns01.slacker.com, ns02.slacker.com)

Analysis

Hierarchy

sdslacker.com sits above dev.sdslacker.com, stg.sdslacker.com and pubstg.sdslacker.com in the domain hierarchy.

Name Servers

Two name servers handle the delegation for sdslacker.com: ns01.slacker.com and ns02.slacker.com.

sdslacker.com delegates to the same name servers as other domains, 14.239.204.in-addr.arpa among them.

There is at least partial name server overlap between sdslacker.com and other domains — ultimatesocialboxing.com, liveone.com, broadbandinstruments.com and two more among them.

These name servers regularly appear alongside ns03.slacker.com, ns01.broadbandinstruments.com, ns02.broadbandinstruments.com and 3 other name servers in NS record sets.

ns01.slacker.com → 204.239.14.11 and ns02.slacker.com → 204.239.14.12: one IP number per host name.

Mail Servers

sdslacker.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

sdslacker.com shares at least some of its mail servers with other domains — for example karmuse.com, ns500841.ns500841.ns500794.ns500841.ns500821.ns500821.ns500821.ns500821.ns500821.ns500821.ns500795.lustypartnersfinder.com, bourdin.name and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to two addresses: 142.250.31.26 and 2607:f8b0:4004:c2d::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.