🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`byteknowledge.com`

DNSSEC	⚠️ Not signed
A	3.230.199.117^{🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix}
		PTR	`static-1a.turbifysites.com`
A	35.168.67.138^{🇺🇸 Amazon35.168.0.0/13 EC2 IAD prefix}
NS	`ns1.turbify.com` ⭐
		A	20.121.230.119^{🇺🇸 Microsoft20.64.0.0/10}
NS	`ns2.turbify.com`
		A	134.33.240.61^{🇬🇧 Microsoft134.33.0.0/16}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f26.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.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	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
SOA	`ns1.turbify.com`hostmaster@byteknowledge.com 2026-02-18 #2

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

Same first word

byteknowledge.net

byteknowledge.dev

byteknowledge.com

Similar names

knowledgebyte.net

knowledgebyte.com

Previous names

Next names

DNS History

17 records (9 active, 8 former)

○NSno-dyn-updates.san.yahoo.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-04-30 07:40:22
● 2017-03-21 12:53:12
○ 2026-08-19 11:14:38
○ 2026-08-29 22:36:10

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

● 2015-07-22 00:16:42
● 2016-04-30 07:40:22
○ 2017-03-21 12:53:12
○ 2026-08-29 22:36:10

●NSns1.turbify.com2026-08-19 → 2026-08-29 · 3 obs

○ 2017-03-21 12:53:12
● 2026-08-19 11:14:38
● 2026-08-29 22:36:10

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

● 2015-07-22 00:16:42
● 2016-04-30 07:40:22
○ 2017-03-21 12:53:12
○ 2026-08-29 22:36:10

●NSns2.turbify.com2026-08-19 → 2026-08-29 · 3 obs

○ 2017-03-21 12:53:12
● 2026-08-19 11:14:38
● 2026-08-29 22:36:10

○NSyns1.yahoo.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-04-30 07:40:22
● 2017-03-21 12:53:12
○ 2026-08-19 11:14:38
○ 2026-08-29 22:36:10

○NSyns2.yahoo.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-04-30 07:40:22
● 2017-03-21 12:53:12
○ 2026-08-19 11:14:38
○ 2026-08-29 22:36:10

●MXalt1.aspmx.l.google.com2015-07-22 → 2026-08-29 · 2 obs

● 2015-07-22 00:16:42
● 2026-08-29 22:36:10

●MXalt2.aspmx.l.google.com2015-07-22 → 2026-08-29 · 2 obs

● 2015-07-22 00:16:42
● 2026-08-29 22:36:10

●MXalt3.aspmx.l.google.com2017-03-21 → 2026-08-29 · 3 obs

○ 2016-04-30 07:40:22
● 2017-03-21 12:53:12
● 2026-08-29 22:36:10

●MXalt4.aspmx.l.google.com2017-03-21 → 2026-08-29 · 3 obs

○ 2016-04-30 07:40:22
● 2017-03-21 12:53:12
● 2026-08-29 22:36:10

●MXaspmx.l.google.com2015-07-22 → 2026-08-29 · 2 obs

● 2015-07-22 00:16:42
● 2026-08-29 22:36:10

○MXaspmx2.googlemail.com2015-07-22 → 2016-04-30 · 4 obs

● 2015-07-22 00:16:42
● 2016-04-30 07:40:22
○ 2017-03-21 12:53:12
○ 2026-08-29 22:36:10

○MXaspmx3.googlemail.com2015-07-22 → 2016-04-30 · 4 obs

● 2015-07-22 00:16:42
● 2016-04-30 07:40:22
○ 2017-03-21 12:53:12
○ 2026-08-29 22:36:10

●A3.230.199.1172026-08-19 → 2026-08-29 · 3 obs

○ 2017-03-21 12:53:12
● 2026-08-19 11:14:38
● 2026-08-29 22:36:10

●A35.168.67.1382026-08-19 → 2026-08-29 · 3 obs

○ 2017-03-21 12:53:12
● 2026-08-19 11:14:38
● 2026-08-29 22:36:10

○A69.195.124.1412015-07-22 → 2017-03-21 · 4 obs

● 2015-07-22 00:16:42
● 2017-03-21 12:53:12
○ 2026-08-19 11:14:38
○ 2026-08-29 22:36:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net...	-
byteknowledge.com	ns1.turbify.com, ns2.turbify.com	2 records

✅ Authoritative Response

Server:134.33.240.61

NS records: ns1.turbify.com, ns2.turbify.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for byteknowledge.com (unsigned zone)

⏱️ Timing

Total: 297ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`35.168.67.138, 3.230.199.117`
NS	2	`ns1.turbify.com, ns2.turbify.com`
MX	5	`ASPMX.L.GOOGLE.com (pri: 1), ALT4.ASPMX.L.GOOGLE.com (pri: 10)...`
SOA	1	`ns1.turbify.com hostmaster.byteknowledge`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.turbify.com, ns2.turbify.com)

Analysis

IP Addresses

byteknowledge.com directs to two IP numbers, 3.230.199.117 and 35.168.67.138

Among the host names that share IP numbers with byteknowledge.com are kathrynkaye-music.net, hrvox.com, willoughbyasia.com and two others.

Name Servers

The NS records for byteknowledge.com delegate to ns1.turbify.com and ns2.turbify.com.

byteknowledge.com has the same name server delegation as a number of other domains, such as hdoutdoor.com, letmedothat.com, abenakiart.org and two more.

byteknowledge.com partially shares its NS delegation with several other domains, including greerscottlaw.com, estelevision.net, hansenergy.in and two others.

These name servers are regularly seen alongside yns1.yahoo.com and yns2.yahoo.com as name servers.

ns1.turbify.com resolves to 20.121.230.119. ns2.turbify.com resolves to 134.33.240.61. Both host names point to a single IP number.

Mail Servers

Mail for byteknowledge.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

byteknowledge.com shares at least some of its mail servers with other domains — for example ftp.unud.ac.id, stromcomm.com, reserveoperationsltd.com and two more.

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

Hosts with two IP numbers each:

The A records for aspmx.l.google.com return 142.251.111.27 and 2607:f8b0:4004:c1f::1a.

The A records for alt1.aspmx.l.google.com return 192.178.234.27 and 2800:3f0:4003:c14::1b.

The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1b.

The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1b.

The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1b.