logswork.com - dns.ninja

`logswork.com`

DNSSEC	⚠️ Not signed
A	162.241.218.67^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
		PTR	`box5543.bluehost.com`
NS	`dns101.register.com` ⭐
		A	162.159.24.117^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`dns102.register.com`
		A	162.159.25.158^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`logswork-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c802::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy4pr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01602.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr05cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch0pr04cu00603.inbound.protection.outlook.com`
		A	52.101.9.21^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00205.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.41.26^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01702.inbound.protection.outlook.com`
		A	52.101.194.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch1pr04cu00103.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`MS=ms26369143`
SOA	`DNS101.REGISTER.com`root@REGISTER.com serial=120081408

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

Same first word

logswork.com

Similar names

logworks.ca

workslog.mx

worklogs.org

worklogs.com

worklogs.de

logworks.co.kr

worklogs.co

logworks.de

logworks.eu

gloworks.tv

workslog.com

gloworks.co.kr

logworks.com

gloworks.com

logworks.com.br

DNS History

11 records (4 active, 7 former)

○NSdns011.b.register.com2015-05-24 → 2017-03-30 · 4 obs

● 2015-05-24 14:25:22
● 2017-03-30 20:14:34
○ 2026-02-17 07:19:36
○ 2026-07-04 20:36:52

●NSdns101.register.com2026-02-17 → 2026-07-04 · 3 obs

○ 2017-03-30 20:14:34
● 2026-02-17 07:19:36
● 2026-07-04 20:36:52

●NSdns102.register.com2026-02-17 → 2026-07-04 · 3 obs

○ 2017-03-30 20:14:34
● 2026-02-17 07:19:36
● 2026-07-04 20:36:52

○NSdns158.c.register.com2015-05-24 → 2017-03-30 · 4 obs

● 2015-05-24 14:25:22
● 2017-03-30 20:14:34
○ 2026-02-17 07:19:36
○ 2026-07-04 20:36:52

○NSdns240.a.register.com2015-05-24 → 2017-03-30 · 4 obs

● 2015-05-24 14:25:22
● 2017-03-30 20:14:34
○ 2026-02-17 07:19:36
○ 2026-07-04 20:36:52

○NSdns249.d.register.com2015-05-24 → 2017-03-30 · 4 obs

● 2015-05-24 14:25:22
● 2017-03-30 20:14:34
○ 2026-02-17 07:19:36
○ 2026-07-04 20:36:52

●MXlogswork-com.mail.protection.outlook.com2017-03-30 → 2026-07-04 · 3 obs

○ 2016-04-10 09:36:08
● 2017-03-30 20:14:34
● 2026-07-04 20:36:52

○MXlogswork.com.inbound10.mxlogic.net2015-05-24 → 2016-04-10 · 4 obs

● 2015-05-24 14:25:22
● 2016-04-10 09:36:08
○ 2017-03-30 20:14:34
○ 2026-07-04 20:36:52

●A162.241.218.672026-02-17 → 2026-07-04 · 3 obs

○ 2017-03-30 20:14:34
● 2026-02-17 07:19:36
● 2026-07-04 20:36:52

○A198.91.90.1352015-05-24 → 2015-05-24 · 3 obs

● 2015-05-24 14:25:22
○ 2015-10-30 03:58:08
○ 2026-07-04 20:36:52

○A52.88.144.1472015-10-30 → 2017-03-30 · 5 obs

○ 2015-05-24 14:25:22
● 2015-10-30 03:58:08
● 2017-03-30 20:14:34
○ 2026-02-17 07:19:36
○ 2026-07-04 20:36:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
logswork.com	dns101.register.com, dns102.register.com	2 records

✅ Authoritative Response

Server:162.159.25.158

NS records: dns101.register.com, dns102.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for logswork.com (unsigned zone)

⏱️ Timing

Total: 184ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.241.218.67`
NS	2	`dns102.register.com, dns101.register.com`
MX	1	`logswork-com.mail.protection.outlook.com`
TXT	2	`MS=ms26369143, v=spf1 include:spf.protection.outlook.co`
SOA	1	`DNS101.REGISTER.com root.REGISTER.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

IP Addresses

logswork.com resolves to just one IP address, 162.241.218.67.

Two other host names, along with yaelbern.com, saqqarasalon.com and mail.dralenefisk.com, also share IP numbers with logswork.com.

Name Servers

DNS delegation for logswork.com points to two name servers: dns101.register.com and dns102.register.com.

logswork.com shares its NS records with other domains, for example eveningpediatrics.com, pppppponline.com, dcs-sadecv.com and two others.

dns101.register.com resolves to 162.159.24.117. dns102.register.com resolves to 162.159.25.158. Both host names point to a single IP number.

Mail Servers

The sole mail server for logswork.com is logswork-com.mail.protection.outlook.com.

With 8 IP addresses total, logswork-com.mail.protection.outlook.com resolves to 52.101.9.21, 52.101.11.15, 52.101.41.26 and 5 others.