bytesignal.com - dns.ninja

`bytesignal.com`

DNSSEC	⚠️ Not signed
A	64.73.207.3^{🇺🇸 Amazon64.73.192.0/19}
NS	`ns20.digicertdns.com` ⭐
		A	2600:1800:10::1:1f^{🇺🇸 Tiggee2600:1800:10::/48 DNS Made Easy anycast network}
			PTR	`ns20.digicertdns.com`
		A	208.94.148.223^{🇺🇸 Tiggee208.94.148.0/24 DNS Made Easy anycast network}
			PTR	`ns20.digicertdns.com`
NS	`ns21.digicertdns.com`
		A	2600:1801:11::1:1f^{🇺🇸 Tiggee2600:1801:11::/48 DNS Made Easy anycast network}
			PTR	`ns21.digicertdns.com`
		A	208.80.124.223^{🇺🇸 Tiggee208.80.124.0/24 DNS Made Easy anycast network}
			PTR	`ns21.digicertdns.com`
NS	`ns22.digicertdns.com`
		A	2600:1802:12::1:1f^{🇺🇸 Tiggee2600:1802:12::/48 DNS Made Easy anycast network}
			PTR	`ns22.digicertdns.com`
		A	208.80.126.223^{🇺🇸 Tiggee208.80.126.0/24 DNS Made Easy anycast network}
			PTR	`ns22.digicertdns.com`
NS	`ns23.digicertdns.net`
		A	2600:1801:13::1:1f^{🇺🇸 Tiggee2600:1801:13::/48 DNS Made Easy anycast network}
			PTR	`ns23.digicertdns.net`
		A	208.80.125.223^{🇺🇸 Tiggee208.80.125.0/24 DNS Made Easy anycast network}
			PTR	`ns23.digicertdns.net`
NS	`ns24.digicertdns.net`
		A	2600:1802:14::1:1f^{🇺🇸 Tiggee2600:1802:14::/48 DNS Made Easy anycast network}
			PTR	`ns24.digicertdns.net`
		A	208.80.127.223^{🇺🇸 Tiggee208.80.127.0/24 DNS Made Easy anycast network}
			PTR	`ns24.digicertdns.net`
NS	`ns25.digicertdns.net` ⚠️ Not in parent delegation
		A	2600:1800:15::1:1f^{🇺🇸 Tiggee2600:1800:15::/48 DNS Made Easy anycast network}
			PTR	`ns25.digicertdns.net`
		A	208.94.149.223^{🇺🇸 Tiggee208.94.149.0/24 DNS Made Easy anycast network}
			PTR	`ns25.digicertdns.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.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::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=bL-BaFv-aVktR-NwwUM8Gq2I3A45X1Xd_qRAev5c-e4`
TXT	`v=spf1 ip4:103.113.161.0/24 include:amazonses.com -all`
TXT	`eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJkb21haW4iOiJieXRlc2lnbmFsLmNvbSIsImV4...`
SOA	`ns20.digicertdns.com`dns@digicertdns.com 2009-01-04 #86

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

Subdomains

mailer.bytesignal.com

media.bytesignal.com

push.bytesignal.com

analytics.bytesignal.com

Same first word

bytesignal.email

bytesignal.com

Similar names

beastingly.com

signalbyte.com

DNS History

22 records (12 active, 10 former)

○NSdns1.name-services.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

○NSdns2.name-services.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

○NSdns3.name-services.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

○NSdns4.name-services.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

○NSdns5.name-services.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

●NSns20.digicertdns.com2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●NSns21.digicertdns.com2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●NSns22.digicertdns.com2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●NSns23.digicertdns.net2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●NSns24.digicertdns.net2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●NSns25.digicertdns.net2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●MXalt1.aspmx.l.google.com2015-08-23 → 2026-07-12 · 2 obs

● 2015-08-23 00:27:50
● 2026-07-12 18:30:54

●MXalt2.aspmx.l.google.com2015-08-23 → 2026-07-12 · 2 obs

● 2015-08-23 00:27:50
● 2026-07-12 18:30:54

●MXalt3.aspmx.l.google.com2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●MXalt4.aspmx.l.google.com2026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

●MXaspmx.l.google.com2015-08-23 → 2026-07-12 · 2 obs

● 2015-08-23 00:27:50
● 2026-07-12 18:30:54

○MXaspmx2.googlemail.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

○MXaspmx3.googlemail.com2015-08-23 → 2016-07-13 · 4 obs

● 2015-08-23 00:27:50
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

○A108.175.149.112015-08-23 → 2015-08-23 · 3 obs

● 2015-08-23 00:27:50
○ 2015-12-14 05:24:06
○ 2026-07-12 18:30:54

○A108.175.149.1282015-12-14 → 2015-12-14 · 4 obs

○ 2015-08-23 00:27:50
● 2015-12-14 05:24:06
○ 2016-03-12 04:50:26
○ 2026-07-12 18:30:54

○A184.168.47.2252016-03-12 → 2016-07-13 · 5 obs

○ 2015-12-14 05:24:06
● 2016-03-12 04:50:26
● 2016-07-13 06:45:02
○ 2026-02-19 01:52:02
○ 2026-07-12 18:30:54

●A64.73.207.32026-02-19 → 2026-07-12 · 3 obs

○ 2016-07-13 06:45:02
● 2026-02-19 01:52:02
● 2026-07-12 18:30:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
bytesignal.com	ns20.digicertdns.com, ns21.digicertdns.com, ns22.digicertdns.com, ns24.digicertdns.net...	6 records

✅ Authoritative Response

Server:208.94.148.223

NS records: ns20.digicertdns.com, ns21.digicertdns.com, ns22.digicertdns.com, ns24.digicertdns.net, ns23.digicertdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bytesignal.com (unsigned zone)

⏱️ Timing

Total: 714ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.73.207.3`
NS	6	`ns22.digicertdns.com, ns24.digicertdns.net...`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 5)...`
TXT	3	`v=spf1 ip4:103.113.161.0/24 include:amaz, google-site-verification=bL-BaFv-aVktR-N...`
SOA	1	`ns20.digicertdns.com dns.digicertdns.com`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns20.digicertdns.com, ns20.digicertdns.com, ns21.digicertdns.com...)

Analysis

Hierarchy

mailer.bytesignal.com, media.bytesignal.com, push.bytesignal.com and analytics.bytesignal.com each fall under the parent domain bytesignal.com.

IP Addresses

bytesignal.com has exactly one IP address — 64.73.207.3.

Name Servers

bytesignal.com is served by 6 authoritative name servers — among them ns20.digicertdns.com, ns21.digicertdns.com, ns22.digicertdns.com and 3 others.

bytesignal.com partially shares its NS delegation with several other domains, including kommo.cc, spconinc.com, accessta.com and two others.

In DNS configurations, these name servers often share authority with ns23.digicertdns.net, ns24.digicertdns.net, ns25.digicertdns.net and 7 other name servers.

Host names pointing to two IP addresses:

ns20.digicertdns.com resolves to two addresses: 208.94.148.223 and 2600:1800:10::1:1f.

ns21.digicertdns.com resolves to two addresses: 208.80.124.223 and 2600:1801:11::1:1f.

ns22.digicertdns.com resolves to two addresses: 208.80.126.223 and 2600:1802:12::1:1f.

ns23.digicertdns.net resolves to two addresses: 208.80.125.223 and 2600:1801:13::1:1f.

ns24.digicertdns.net resolves to two addresses: 208.80.127.223 and 2600:1802:14::1:1f.

ns25.digicertdns.net resolves to two addresses: 208.94.149.223 and 2600:1800:15::1:1f.

Mail Servers

Mail for bytesignal.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.

At least some of the mail servers used by bytesignal.com are shared with other domains: lasseleegaard.net, t3.training, pinkadoo.com and two others among them.

These mail servers are often deployed together with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com resolves to two addresses: 192.178.155.26 and 2607:f8b0:4004:c1b::1a.

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.27 and 2a00:1450:400b:c02::1a.

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.27 and 2a00:1450:400c:c23::1b.