syncbyte.in - dns.ninja

`syncbyte.in`

DNSSEC	⚠️ Not signed
A	64.29.17.1^{🇺🇸 Amazon64.29.17.0/24 EC2 Prefix}
A	64.29.17.65^{🇺🇸 Amazon64.29.17.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	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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::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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.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`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1778564973

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns.trs-dns.com` ⭐
	NS	`ns1.registry.in`
	NS	`ns2.registry.in`
	NS	`ns3.registry.in`
	NS	`ns4.registry.in`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1785196554

Same first word

syncbyte.com

syncbyte.com.sg

syncbyte.de

syncbyte.in

Similar names

bytesync.org

bytesync.click

bytesync.com

bytesync.net

DNS History

18 records (9 active, 9 former)

○NSjns1.dailyrazor.com2026-04-10 → 2026-04-10 · 4 obs

○ 2019-01-07 02:15:48
● 2026-04-10 16:37:16
○ 2026-06-09 03:25:48
○ 2026-07-28 00:23:48

○NSjns2.dailyrazor.com2026-04-10 → 2026-04-10 · 4 obs

○ 2019-01-07 02:15:48
● 2026-04-10 16:37:16
○ 2026-06-09 03:25:48
○ 2026-07-28 00:23:48

○NSjns3.dailyrazor.com2026-04-10 → 2026-04-10 · 4 obs

○ 2019-01-07 02:15:48
● 2026-04-10 16:37:16
○ 2026-06-09 03:25:48
○ 2026-07-28 00:23:48

○NSjns4.dailyrazor.com2026-04-10 → 2026-04-10 · 4 obs

○ 2019-01-07 02:15:48
● 2026-04-10 16:37:16
○ 2026-06-09 03:25:48
○ 2026-07-28 00:23:48

○NSns1.arrowsupercloud.com2019-01-07 → 2019-01-07 · 3 obs

● 2019-01-07 02:15:48
○ 2026-04-10 16:37:16
○ 2026-07-28 00:23:48

●NSns1.vercel-dns.com2026-06-09 → 2026-07-28 · 3 obs

○ 2026-04-10 16:37:16
● 2026-06-09 03:25:48
● 2026-07-28 00:23:48

○NSns2.arrowsupercloud.com2019-01-07 → 2019-01-07 · 3 obs

● 2019-01-07 02:15:48
○ 2026-04-10 16:37:16
○ 2026-07-28 00:23:48

●NSns2.vercel-dns.com2026-06-09 → 2026-07-28 · 3 obs

○ 2026-04-10 16:37:16
● 2026-06-09 03:25:48
● 2026-07-28 00:23:48

●MXalt1.aspmx.l.google.com2019-01-07 → 2026-07-28 · 2 obs

● 2019-01-07 02:15:48
● 2026-07-28 00:23:48

●MXalt2.aspmx.l.google.com2019-01-07 → 2026-07-28 · 2 obs

● 2019-01-07 02:15:48
● 2026-07-28 00:23:48

●MXalt3.aspmx.l.google.com2019-01-07 → 2026-07-28 · 2 obs

● 2019-01-07 02:15:48
● 2026-07-28 00:23:48

●MXalt4.aspmx.l.google.com2019-01-07 → 2026-07-28 · 2 obs

● 2019-01-07 02:15:48
● 2026-07-28 00:23:48

●MXaspmx.l.google.com2019-01-07 → 2026-07-28 · 2 obs

● 2019-01-07 02:15:48
● 2026-07-28 00:23:48

○A15.204.212.462026-04-10 → 2026-04-10 · 4 obs

○ 2019-01-07 02:15:48
● 2026-04-10 16:37:16
○ 2026-06-09 03:25:48
○ 2026-07-28 00:23:48

○A216.198.79.652026-06-09 → 2026-06-09 · 4 obs

○ 2026-04-10 16:37:16
● 2026-06-09 03:25:48
○ 2026-07-28 00:23:46
○ 2026-07-28 00:23:48

●A64.29.17.12026-06-09 → 2026-07-28 · 6 obs

○ 2026-04-10 16:37:16
● 2026-06-09 03:25:48
● 2026-06-10 03:47:24
○ 2026-06-25 20:23:44
● 2026-07-28 00:23:46
● 2026-07-28 00:23:48

●A64.29.17.652026-06-25 → 2026-07-28 · 3 obs

○ 2026-06-10 03:47:24
● 2026-06-25 20:23:44
● 2026-07-28 00:23:48

○A66.85.138.702019-01-07 → 2019-01-07 · 3 obs

● 2019-01-07 02:15:48
○ 2026-04-10 16:37:16
○ 2026-07-28 00:23:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns1.registry.in, ns3.registry.in, ns2.registry.in, ns4.registry.in	-
syncbyte.in	ns1.vercel-dns.com, ns2.vercel-dns.com	-

✅ Authoritative Response

Server:198.51.45.13

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for syncbyte.in (unsigned zone)

⏱️ Timing

Total: 430ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`64.29.17.65, 216.198.79.65`
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

Analysis

IP Addresses

syncbyte.in has two IP addresses: 64.29.17.1 and 64.29.17.65

Among the host names that share IP numbers with syncbyte.in are apayu.kr, starbase.com.au, vn.quayphim.net and two others.

Name Servers

Two name servers handle the delegation for syncbyte.in: ns1.vercel-dns.com and ns2.vercel-dns.com.

syncbyte.in has the same name server delegation as a number of other domains, such as glau.com.vc, cdmxbitdevs.com, azulwebdev.com and two more.

syncbyte.in shares at least some of its name servers with other domains, for example joyofelixir.com, devcodegroup.com, 201created.se and theia-tracking.de.

These name servers tend to be used in conjunction with the name servers a.zeit-world.co.uk.

ns1.vercel-dns.com and ns2.vercel-dns.com both carry two IP addresses. The A records for ns1.vercel-dns.com are 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1; the A records for ns2.vercel-dns.com are 198.51.45.13 and 2a00:edc0:6259:7:13::2.

Mail Servers

Five mail servers handle syncbyte.in: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

syncbyte.in shares at least some of its mail servers with other domains — for example lachance.paris, ns500698.ns500759.ns500698.ns500758.ns500736.ns500736.ns500736.ns500735.ns500735.ns500708.ns500708.ns500708.ns500708.ns500576.ns500619.ns500652.ns500619.trackreceptor.com, comvast.net 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 resolves to two addresses: 192.178.155.26 and 2607:f8b0:4004:c27::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

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

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

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