fetchbyte.com - dns.ninja

`fetchbyte.com`

DNSSEC	⚠️ Not signed
A	52.20.84.62^{🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix}
		PTR	`ec2-52-20-84-62.compute-1.amazonaws.com`
NS	`ns1.atom.com` ⭐
		A	44.219.81.145^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-219-81-145.compute-1.amazonaws.com`
NS	`ns2.atom.com`
		A	50.19.240.86^{🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix}
			PTR	`ec2-50-19-240-86.compute-1.amazonaws.com`
MX	`mx1.forwardemail.net` ⭐
		A	2604:a880:2:d0::306:1^{🇺🇸 DIGITALOCEAN2604:a880:2::/48 DigitalOcean}
			PTR	`mx1.forwardemail.net`
		A	2a02:6ea0:d71e::2^{🇺🇸 CDN772a02:6ea0:d700::/40 Denver IPv6}
			PTR	`mx1.forwardemail.net`
		A	121.127.44.56^{🇺🇸 CDN77121.127.44.0/24 Denver}
			PTR	`mx1.forwardemail.net`
		A	138.197.213.185^{🇺🇸 DIGITALOCEAN138.197.208.0/20 DigitalOcean}
			PTR	`mx1.forwardemail.net`
MX	`mx2.forwardemail.net` ⭐
		A	2604:a880:400:d1::cd:9001^{🇺🇸 DIGITALOCEAN2604:a880:400::/48 DigitalOcean}
			PTR	`mx2.forwardemail.net`
		A	2a02:6ea0:d71e::1^{🇺🇸 CDN772a02:6ea0:d700::/40 Denver IPv6}
			PTR	`mx2.forwardemail.net`
		A	104.248.224.170^{🇺🇸 DIGITALOCEAN104.248.224.0/20 DigitalOcean}
			PTR	`mx2.forwardemail.net`
		A	121.127.44.59^{🇺🇸 CDN77121.127.44.0/24 Denver}
			PTR	`mx2.forwardemail.net`
TXT	`f0095018235b8109a2bf9f65674a1784b6971ed6`
TXT	`afternic-verification-jpmCrsamjXFGeiF26QG3ok`
TXT	`forward-email-site-verification=xKDo9aDqkP`
TXT	`4b5812ec-3128-4cb8-9078-83f2d82c451e`
SOA	`ns1.atom.com`hostmaster@fetchbyte.com 2026-02-11 #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=1780988186

Same first word

fetchbyte.com

Similar names

bytefetch.co.uk

bytefetch.net

chefbetty.com

bytefetch.com

bytefetch.us

bytefetch.de

DNS History

13 records (5 active, 8 former)

○NSdns1.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

○NSdns2.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

●NSns1.atom.com2026-04-09 → 2026-06-09 · 3 obs

○ 2020-02-26 16:43:50
● 2026-04-09 05:46:06
● 2026-06-09 07:10:30

●NSns2.atom.com2026-04-09 → 2026-06-09 · 3 obs

○ 2020-02-26 16:43:50
● 2026-04-09 05:46:06
● 2026-06-09 07:10:30

○MXeforward1.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

○MXeforward2.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

○MXeforward3.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

○MXeforward4.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

○MXeforward5.registrar-servers.com2020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

●MXmx1.forwardemail.net2026-04-09 → 2026-06-09 · 3 obs

○ 2020-02-26 16:43:50
● 2026-04-09 05:46:06
● 2026-06-09 07:10:30

●MXmx2.forwardemail.net2026-04-09 → 2026-06-09 · 3 obs

○ 2020-02-26 16:43:50
● 2026-04-09 05:46:06
● 2026-06-09 07:10:30

○A192.64.119.1922020-02-26 → 2020-02-26 · 3 obs

● 2020-02-26 16:43:50
○ 2026-04-09 05:46:06
○ 2026-06-09 07:10:30

●A52.20.84.622026-04-09 → 2026-06-09 · 3 obs

○ 2020-02-26 16:43:50
● 2026-04-09 05:46:06
● 2026-06-09 07:10:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
fetchbyte.com	ns1.atom.com, ns2.atom.com	2 records

✅ Authoritative Response

Server:44.219.81.145

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fetchbyte.com (unsigned zone)

⏱️ Timing

Total: 3135ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.20.84.62`
NS	2	`ns1.atom.com, ns2.atom.com`
MX	2	`mx2.forwardemail.net (pri: 10), mx1.forwardemail.net (pri: 10)`
TXT	4	`forward-email-site-verification=xKDo9aDq, afternic-verification-jpmCrsamjXFGeiF26Q...`
SOA	1	`ns1.atom.com hostmaster.fetchbyte.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

fetchbyte.com resolves to one IP address: 52.20.84.62.

escona.com, pulsegen.com, lasirena.com and two other host names share IP numbers with fetchbyte.com.

Name Servers

fetchbyte.com uses two name servers for its delegation: ns1.atom.com and ns2.atom.com.

fetchbyte.com uses the same name servers as several other domains — among them ormaro.com, mooan.com, flexured.com and two more.

At least some of fetchbyte.com's name servers are shared with other domains, for example fleamart.org, forhost.com, cleanhale.com and two more.

These name servers tend to be used in conjunction with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.

Each of ns1.atom.com and ns2.atom.com has one IP address: ns1.atom.com uses 44.219.81.145 and ns2.atom.com uses 50.19.240.86.

Mail Servers

Mail for fetchbyte.com is handled by two mail servers — mx1.forwardemail.net and mx2.forwardemail.net.

fetchbyte.com uses an identical mail server configuration to several other domains — among them www.resona.nl, airtel.ga, givehopeinternational.com and two more.

At least some of fetchbyte.com's mail servers are shared with other domains, among them jeps.fi, lebanon-flora.org and dabool.com.

mx1.forwardemail.net and mx2.forwardemail.net are two hostnames, each pointing to 4 IP numbers: mx1.forwardemail.net directs to 121.127.44.56, 138.197.213.185, 2604:a880:2:d0::306:1 and 2a02:6ea0:d71e::2; mx2.forwardemail.net directs to 104.248.224.170, 121.127.44.59, 2604:a880:400:d1::cd:9001 and 2a02:6ea0:d71e::1.