yieldlogic.com - dns.ninja

`yieldlogic.com`

DNSSEC	⚠️ Not signed
A	208.91.197.39^{🇻🇬 CONFLUENCE-NETWORK-INC208.91.197.0/24 Confluence Networks Route Object}
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	`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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com` ⭐
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 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::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
SOA	`DNS101.REGISTER.com`root@REGISTER.com serial=120042815

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

Subdomains

ns1.yieldlogic.com

Same first word

yieldlogic.com

DNS History

16 records (8 active, 8 former)

○NSdns010.d.register.com2017-01-07 → 2017-12-23 · 5 obs

○ 2016-04-22 05:38:22
● 2017-01-07 23:01:40
● 2017-12-23 19:52:20
○ 2026-02-18 13:59:20
○ 2026-07-04 20:41:42

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

○ 2017-12-23 19:52:20
● 2026-02-18 13:59:20
● 2026-07-04 20:41:42

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

○ 2017-12-23 19:52:20
● 2026-02-18 13:59:20
● 2026-07-04 20:41:42

○NSdns111.a.register.com2017-01-07 → 2017-12-23 · 5 obs

○ 2016-04-22 05:38:22
● 2017-01-07 23:01:40
● 2017-12-23 19:52:20
○ 2026-02-18 13:59:20
○ 2026-07-04 20:41:42

○NSdns141.c.register.com2017-01-07 → 2017-12-23 · 5 obs

○ 2016-04-22 05:38:22
● 2017-01-07 23:01:40
● 2017-12-23 19:52:20
○ 2026-02-18 13:59:20
○ 2026-07-04 20:41:42

○NSdns228.b.register.com2017-01-07 → 2017-12-23 · 5 obs

○ 2016-04-22 05:38:22
● 2017-01-07 23:01:40
● 2017-12-23 19:52:20
○ 2026-02-18 13:59:20
○ 2026-07-04 20:41:42

○NSns1.bluehost.com2015-07-04 → 2016-04-22 · 4 obs

● 2015-07-04 20:59:06
● 2016-04-22 05:38:22
○ 2017-01-07 23:01:40
○ 2026-07-04 20:41:42

○NSns1.yieldlogic.com2015-07-04 → 2016-04-22 · 4 obs

● 2015-07-04 20:59:06
● 2016-04-22 05:38:22
○ 2017-01-07 23:01:40
○ 2026-07-04 20:41:42

○NSns2.bluehost.com2015-07-04 → 2016-04-22 · 4 obs

● 2015-07-04 20:59:06
● 2016-04-22 05:38:22
○ 2017-01-07 23:01:40
○ 2026-07-04 20:41:42

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

● 2015-07-04 20:59:06
● 2026-07-04 20:41:42

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

● 2015-07-04 20:59:06
● 2026-07-04 20:41:42

●MXalt3.aspmx.l.google.com2015-07-04 → 2026-07-04 · 2 obs

● 2015-07-04 20:59:06
● 2026-07-04 20:41:42

●MXalt4.aspmx.l.google.com2015-07-04 → 2026-07-04 · 2 obs

● 2015-07-04 20:59:06
● 2026-07-04 20:41:42

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

● 2015-07-04 20:59:06
● 2026-07-04 20:41:42

○A192.163.237.2292015-07-04 → 2016-04-22 · 4 obs

● 2015-07-04 20:59:06
● 2016-04-22 05:38:22
○ 2017-01-07 23:01:40
○ 2026-07-04 20:41:42

●A208.91.197.392017-01-07 → 2026-07-04 · 3 obs

○ 2016-04-22 05:38:22
● 2017-01-07 23:01:40
● 2026-07-04 20:41:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, g.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net...	-
yieldlogic.com	dns101.register.com, dns102.register.com	2 records

✅ Authoritative Response

Server:162.159.24.117

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for yieldlogic.com (unsigned zone)

⏱️ Timing

Total: 237ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`208.91.197.39`
NS	2	`dns102.register.com, dns101.register.com`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 10)...`
SOA	1	`DNS101.REGISTER.com root.REGISTER.com`

📌 Glue Records Collected

Total: 2

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

Analysis

Hierarchy

ns1.yieldlogic.com is a subdomain of yieldlogic.com.

IP Addresses

yieldlogic.com directs to one IP number, which is 208.91.197.39.

Among the host names that share IP numbers with yieldlogic.com are newsconsulting.com, 193-137-12-86.static.winehousetribute.com, lomdus.com and two others.

Name Servers

yieldlogic.com is served by two delegated name servers, dns101.register.com and dns102.register.com.

yieldlogic.com has the same name server delegation as a number of other domains, such as milnerpropertiesllc.com, berriochoa.com, childdevelopmentspecialist.org and two more.

The name servers for yieldlogic.com overlap at least in part with those of other domains, including rickysteele.net and talkover.net.

Both dns101.register.com and dns102.register.com have a single IP address each — dns101.register.com resolves to 162.159.24.117 while dns102.register.com resolves to 162.159.25.158.

Mail Servers

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

yieldlogic.com shares at least some of its mail servers with other domains — for example alchemylaw.com, midwestfabrics.com, tapglance.com and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com maps to two IP addresses — 142.251.179.26 and 2607:f8b0:4004:c1d::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.27 and 2a00:1450:400c:c23::1a.