🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`bytes4bytes.com`

DNSSEC	⚠️ Not signed
A	66.33.60.130^{🇺🇸 Amazon66.33.60.0/24 EC2 Prefix}
A	76.76.21.164^{🇺🇸 Amazon76.76.21.0/24 EC2 Prefix}
NS	`ns1.vercel-dns.com` ⭐
		A	2620:4d:4000:6259:7:13:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p13.nsone.net`
		A	198.51.44.13^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p13.nsone.net`
NS	`ns2.vercel-dns.com`
		A	2a00:edc0:6259:7:13::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p13.nsone.net`
		A	198.51.45.13^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns2.p13.nsone.net`
MX	`bytes4bytes-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c927::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn0pr04cu00907.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:f907::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm1pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00200.inbound.protection.outlook.com`
		A	52.101.41.201^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr03cu00201.inbound.protection.outlook.com`
		A	52.101.42.14^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr04cu00106.inbound.protection.outlook.com`
		A	52.101.60.173^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn3pr0501cu00105.inbound.protection.outlook.com`
		A	52.101.194.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00504.inbound.protection.outlook.com`
MX	`aspmx.l.google.com`⁽¹⁾
		A	2607:f8b0:4004:c2d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ry-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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	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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
MX	`kf7a5p6r4w6t2qj52woieszp5svkoafxemj4525bvegi4qtrqkfa.mx-verification.google.com`⁽¹⁵⁾
TXT	`MS=ms41749215`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1666677544

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

Same first word

bytes4bytes.com

Previous names

Next names

DNS History

27 records (11 active, 16 former)

○NSns03.domaincontrol.com2018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○NSns04.domaincontrol.com2018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

●NSns1.vercel-dns.com2026-09-19 → 2026-09-24 · 3 obs

○ 2018-08-07 00:53:44
● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●NSns2.vercel-dns.com2026-09-19 → 2026-09-24 · 3 obs

○ 2018-08-07 00:53:44
● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXalt1.aspmx.l.google.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXalt2.aspmx.l.google.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXalt3.aspmx.l.google.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXalt4.aspmx.l.google.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXaspmx.l.google.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXbytes4bytes-com.mail.protection.outlook.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

●MXkf7a5p6r4w6t2qj52woieszp5svkoafxemj4525bvegi4qtrqkfa.mx-verification.google.com2026-09-19 → 2026-09-24 · 2 obs

● 2026-09-19 12:06:22
● 2026-09-24 03:28:58

○A184.168.221.322018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A184.168.221.372018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A184.168.221.412018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A184.168.221.552018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A50.63.202.372018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A50.63.202.522018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A50.63.202.572018-08-07 → 2018-08-07 · 4 obs

● 2018-08-07 00:53:08
● 2018-08-07 00:53:44
○ 2026-09-19 12:06:22
○ 2026-09-24 03:28:58

○A66.33.60.1292026-09-23 → 2026-09-23 · 4 obs

○ 2026-09-23 10:22:46
● 2026-09-23 21:54:26
○ 2026-09-24 03:28:52
○ 2026-09-24 03:28:58

●A66.33.60.1302026-09-24 → 2026-09-24 · 3 obs

○ 2026-09-23 21:54:26
● 2026-09-24 03:28:52
● 2026-09-24 03:28:58

○A66.33.60.1932026-09-19 → 2026-09-23 · 6 obs

○ 2026-09-19 12:06:22
● 2026-09-19 22:02:36
○ 2026-09-20 23:31:48
● 2026-09-23 10:22:46
○ 2026-09-23 21:54:26
○ 2026-09-24 03:28:58

○A66.33.60.1942026-09-19 → 2026-09-19 · 4 obs

○ 2026-09-19 12:06:22
● 2026-09-19 22:02:36
○ 2026-09-23 10:22:46
○ 2026-09-24 03:28:58

○A66.33.60.352026-09-19 → 2026-09-19 · 4 obs

○ 2018-08-07 00:53:44
● 2026-09-19 12:06:22
○ 2026-09-19 22:02:36
○ 2026-09-24 03:28:58

○A76.76.21.1232026-09-20 → 2026-09-20 · 4 obs

○ 2026-09-19 22:02:36
● 2026-09-20 23:31:48
○ 2026-09-23 10:22:46
○ 2026-09-24 03:28:58

●A76.76.21.1642026-09-24 → 2026-09-24 · 3 obs

○ 2026-09-23 21:54:26
● 2026-09-24 03:28:52
● 2026-09-24 03:28:58

○A76.76.21.222026-09-19 → 2026-09-23 · 6 obs

○ 2018-08-07 00:53:44
● 2026-09-19 12:06:22
○ 2026-09-19 22:02:36
● 2026-09-23 21:54:26
○ 2026-09-24 03:28:52
○ 2026-09-24 03:28:58

○A76.76.21.2412026-09-23 → 2026-09-23 · 4 obs

○ 2026-09-20 23:31:48
● 2026-09-23 10:22:46
○ 2026-09-23 21:54:26
○ 2026-09-24 03:28:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, e.gtld-servers.net...	-
bytes4bytes.com	ns1.vercel-dns.com, ns2.vercel-dns.com	4 records

✅ Authoritative Response

Server:198.51.44.13

NS records: ns1.vercel-dns.com, ns2.vercel-dns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bytes4bytes.com (unsigned zone)

⏱️ Timing

Total: 418ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`66.33.60.35, 76.76.21.98`
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
MX	7	`bytes4bytes-com.mail.protection.outlook., aspmx.l.google.com (pri: 1)...`
TXT	2	`MS=ms41749215, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.vercel-dns.com, ns1.vercel-dns.com, ns2.vercel-dns.com...)

Analysis

IP Addresses

bytes4bytes.com points to the IP addresses 66.33.60.130 and 76.76.21.164

Additional host names — mx.neilheffernan.com, guidesummit.com, panasonic.vercel.joyn.de and two others — share IP numbers with bytes4bytes.com.

Name Servers

bytes4bytes.com has two authoritative name servers — ns1.vercel-dns.com and ns2.vercel-dns.com.

bytes4bytes.com shares its name server setup with other domains, including oakleafresidency.com, dirigoai.tech, cloudcontract-recruit.com and two others.

The name servers for bytes4bytes.com overlap at least in part with those of other domains, including aryangarg.dev and myracl.in.

Both ns1.vercel-dns.com and ns2.vercel-dns.com have two IP addresses each. ns1.vercel-dns.com resolves to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1; ns2.vercel-dns.com resolves to 198.51.45.13 and 2a00:edc0:6259:7:13::2.

Mail Servers

bytes4bytes.com has 7 mail servers — aspmx.l.google.com, kf7a5p6r4w6t2qj52woieszp5svkoafxemj4525bvegi4qtrqkfa.mx-verification.google.com, alt1.aspmx.l.google.com plus 4 other.

bytes4bytes.com shares mail servers — at least in part — with other domains, including kbcchannel.tv, queencitypercussion.com, firstclassdelegation.com and two others.

These mail servers are frequently used alongside the mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com, plus two others.

Host names with two IP numbers:

aspmx.l.google.com resolves to 192.178.155.27 and 2607:f8b0:4004:c2d::1a.

Host names with 8 IP numbers:

bytes4bytes-com.mail.protection.outlook.com points to 52.101.41.201, 52.101.42.14, 52.101.60.173 and 5 other IP addresses.

Host names with two IP numbers:

alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.

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

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

alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.