`workingsecurity.com`

DNSSEC	⚠️ Not signed
A	34.174.129.116^{🇺🇸 Google34.174.128.0/17}
		PTR	`116.129.174.34.bc.googleusercontent.com`
NS	`ns1.siteground.net` ⭐
		A	75.2.77.104^{🇺🇸 Amazon75.2.64.0/20}
			PTR	`ac4b097dbd0dd6307.awsglobalaccelerator.com`
NS	`ns2.siteground.net`
		A	99.83.229.113^{🇺🇸 Amazon99.83.224.0/20}
			PTR	`ac4b097dbd0dd6307.awsglobalaccelerator.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c03::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dy-in-f26.1e100.net`
		A	74.125.137.26^{🇺🇸 Google74.125.137.0/24}
			PTR	`dy-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f27.1e100.net`
		A	192.178.128.26^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4023:1015::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f26.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.26^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f26.1e100.net`
TXT	`google-site-verification=dXMs5jsspOg7BOdt8TTf3EBXES0IXangp-k1E7kYNVg`
TXT	`google-site-verification=j9CeISUsmBat3keuMTJhEpy1qQwGRYMi07vyaNtOjqY`
TXT	`_globalsign-domain-verification=6pjBv_QzHnntvIALQPeoPtyzimpxZ_DXQVTSnZ-iDX`
TXT	`v=spf1 include:_spf.google.com include:workingsecurity.com.spf.auto.dnssmarth...`
SOA	`ns1.siteground.net`dnsadmin@serv01.siteground138.com 2020-12-04 #4

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

Same first word

workingsecurity.com

DNS History

16 records (8 active, 8 former)

●NSns1.siteground.net2026-04-09 → 2026-04-23 · 3 obs

○ 2017-06-18 12:03:20
● 2026-04-09 12:29:08
● 2026-04-23 11:48:52

○NSns1.siteground138.com2015-12-13 → 2017-06-18 · 5 obs

○ 2015-08-08 10:13:46
● 2015-12-13 16:25:16
● 2017-06-18 12:03:20
○ 2026-04-09 12:29:08
○ 2026-04-23 11:48:52

●NSns2.siteground.net2026-04-09 → 2026-04-23 · 3 obs

○ 2017-06-18 12:03:20
● 2026-04-09 12:29:08
● 2026-04-23 11:48:52

○NSns2.siteground138.com2015-12-13 → 2017-06-18 · 5 obs

○ 2015-08-08 10:13:46
● 2015-12-13 16:25:16
● 2017-06-18 12:03:20
○ 2026-04-09 12:29:08
○ 2026-04-23 11:48:52

○NSns47.domaincontrol.com2015-08-08 → 2015-08-08 · 3 obs

● 2015-08-08 10:13:46
○ 2015-12-13 16:25:16
○ 2026-04-23 11:48:52

○NSns48.domaincontrol.com2015-08-08 → 2015-08-08 · 3 obs

● 2015-08-08 10:13:46
○ 2015-12-13 16:25:16
○ 2026-04-23 11:48:52

●MXalt1.aspmx.l.google.com2015-08-08 → 2026-04-23 · 2 obs

● 2015-08-08 10:13:46
● 2026-04-23 11:48:52

●MXalt2.aspmx.l.google.com2015-08-08 → 2026-04-23 · 2 obs

● 2015-08-08 10:13:46
● 2026-04-23 11:48:52

●MXalt3.aspmx.l.google.com2015-12-13 → 2026-04-23 · 3 obs

○ 2015-08-08 10:13:46
● 2015-12-13 16:25:16
● 2026-04-23 11:48:52

●MXalt4.aspmx.l.google.com2015-12-13 → 2026-04-23 · 3 obs

○ 2015-08-08 10:13:46
● 2015-12-13 16:25:16
● 2026-04-23 11:48:52

●MXaspmx.l.google.com2015-08-08 → 2026-04-23 · 2 obs

● 2015-08-08 10:13:46
● 2026-04-23 11:48:52

○MXaspmx2.googlemail.com2015-08-08 → 2015-08-08 · 3 obs

● 2015-08-08 10:13:46
○ 2015-12-13 16:25:16
○ 2026-04-23 11:48:52

○MXaspmx3.googlemail.com2015-08-08 → 2015-08-08 · 3 obs

● 2015-08-08 10:13:46
○ 2015-12-13 16:25:16
○ 2026-04-23 11:48:52

○A184.154.237.1042015-12-13 → 2017-06-18 · 5 obs

○ 2015-08-08 10:13:46
● 2015-12-13 16:25:16
● 2017-06-18 12:03:20
○ 2026-04-09 12:29:08
○ 2026-04-23 11:48:52

●A34.174.129.1162026-04-09 → 2026-04-23 · 3 obs

○ 2017-06-18 12:03:20
● 2026-04-09 12:29:08
● 2026-04-23 11:48:52

○A72.167.223.1282015-08-08 → 2015-08-08 · 3 obs

● 2015-08-08 10:13:46
○ 2015-12-13 16:25:16
○ 2026-04-23 11:48:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
workingsecurity.com	ns1.siteground.net, ns2.siteground.net	-

✅ Authoritative Response

Server:99.83.229.113

NS records: ns1.siteground.net, ns2.siteground.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for workingsecurity.com (unsigned zone)

⏱️ Timing

Total: 251ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`34.174.129.116`
NS	2	`ns1.siteground.net, ns2.siteground.net`
MX	5	`alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...`
TXT	4	`google-site-verification=dXMs5jsspOg7BOd, google-site-verification=j9CeISUsmBat3ke...`
SOA	1	`ns1.siteground.net dnsadmin.serv01.siteg`

Analysis

IP Addresses

workingsecurity.com points to IP number 34.174.129.116.

Other host names, for example 116.129.174.34.bc.googleusercontent.com and lucidlot.com, share IPs with workingsecurity.com.

Name Servers

workingsecurity.com is delegated to two name servers: ns1.siteground.net and ns2.siteground.net.

workingsecurity.com uses the same name server setup as other domains such as covernow.org, kiriom.net, mundoski.com, cleanstreakllc.com and ceevia.com.

workingsecurity.com shares name servers with other domains at least partially, for example zproekt.com, dreamzcasino.com, trousseau.com.br, fc.football and musicedtech.com.