bytelecom.com.br - dns.ninja

`bytelecom.com.br`

DNSSEC	⚠️ Not signed
A	185.230.63.107^{🇺🇸 wix_com185.230.63.0/24}
		PTR	`unalocated.63.wixsite.com`
NS	`ns1.task.com.br` ⭐
		A	2804:4f0::13^{🇧🇷 AS221292804:4f0::/32 G8 Networks}
		A	200.162.176.13^{🇧🇷 AS22129200.162.176.0/21}
			PTR	`200-162-176-18.task.com.br`
NS	`ns2.task.com.br`
		A	2607:f0d0:1f01:41::4^{🇺🇸 SOFTLAYER2607:f0d0:1f00::/40 -DAL12}
			PTR	`2607.f0d0.1f01.0041.0000.0000.0000.0004-ip6.static.sl-reverse.com`
		A	169.61.136.60^{🇺🇸 SOFTLAYER169.61.128.0/18 -dal12}
			PTR	`mnt3.task.com.br`
NS	`ns3.task.com.br`
		A	2607:f0d0:1f01:41::3^{🇺🇸 SOFTLAYER2607:f0d0:1f00::/40 -DAL12}
			PTR	`2607.f0d0.1f01.0041.0000.0000.0000.0003-ip6.static.sl-reverse.com`
		A	169.61.160.3^{🇺🇸 SOFTLAYER169.61.128.0/18 -dal12}
			PTR	`ns3.task.com.br`
NS	`ns4.task.com.br`
		A	2604:a880:800:10::d1:5001^{🇺🇸 DIGITALOCEAN2604:a880:800::/48 DigitalOcean}
			PTR	`ns4.task.com.br`
		A	104.131.19.139^{🇺🇸 DIGITALOCEAN104.131.0.0/18 DigitalOcean}
			PTR	`ns4.task.com.br`
MX	`mx2.task.com.br` ⭐
		A	177.93.104.137^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd6.task.com.br`
		A	177.93.104.141^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd7.task.com.br`
		A	177.93.104.145^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd8.task.com.br`
		A	177.93.104.149^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd9.task.com.br`
		A	177.93.104.153^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd10.task.com.br`
		A	177.93.104.157^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd11.task.com.br`
MX	`mx4.task.com.br`⁽¹⁰⁰⁾
		A	177.93.104.137^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd6.task.com.br`
		A	177.93.104.141^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd7.task.com.br`
		A	177.93.104.145^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd8.task.com.br`
		A	177.93.104.149^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd9.task.com.br`
		A	177.93.104.153^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd10.task.com.br`
		A	177.93.104.157^{🇧🇷 EVEO177.93.104.0/23 This route object is for a UPX Technologies customer route, which is being exported under this origin AS. This route object was created because no existing route object with the same origin was found, and since some UPX peers filter based on these objects this route may be rejected if this object is not created. Please contact noc@upx.com.br if you have any questions regarding this object.}
			PTR	`mx2-sd11.task.com.br`
TXT	`v=spf1 mx a:smtp.task.com.br include:task.com.br -all`
SOA	`ns1.task.com.br`marcus@task.com.br serial=1773843399

`com.br`

	DNSSEC	⚠️ Not signed
	NS	`a.dns.br` ⭐ ⚠️ Not in parent delegation
	NS	`b.dns.br` ⚠️ Not in parent delegation
	NS	`c.dns.br` ⚠️ Not in parent delegation
	NS	`d.dns.br` ⚠️ Not in parent delegation
	NS	`e.dns.br` ⚠️ Not in parent delegation
	NS	`f.dns.br` ⚠️ Not in parent delegation
	SOA	`a.dns.br`hostmaster@registro.br serial=2026182476

rank #539713 globally
rank #4008 in the tld
WOT: SAFE (69/100)

Same first word

bytelecom.com

bytelecom.az

bytelecom.net.au

bytelecom.com.br

Similar names

ybtelecom.com

DNS History

11 records (7 active, 4 former)

●NSns1.task.com.br2015-08-13 → 2026-07-01 · 2 obs

● 2015-08-13 08:10:22
● 2026-07-01 20:11:06

●NSns2.task.com.br2015-08-13 → 2026-07-01 · 2 obs

● 2015-08-13 08:10:22
● 2026-07-01 20:11:06

●NSns3.task.com.br2015-08-13 → 2026-07-01 · 2 obs

● 2015-08-13 08:10:22
● 2026-07-01 20:11:06

●NSns4.task.com.br2015-08-13 → 2026-07-01 · 2 obs

● 2015-08-13 08:10:22
● 2026-07-01 20:11:06

●MXmx2.task.com.br2015-08-13 → 2026-07-01 · 2 obs

● 2015-08-13 08:10:22
● 2026-07-01 20:11:06

●MXmx4.task.com.br2015-08-13 → 2026-07-01 · 2 obs

● 2015-08-13 08:10:22
● 2026-07-01 20:11:06

○A174.36.74.1082015-08-13 → 2015-12-11 · 4 obs

● 2015-08-13 08:10:22
● 2015-12-11 23:36:46
○ 2016-06-26 15:44:26
○ 2026-07-01 20:11:06

○A174.36.74.1192016-06-26 → 2017-02-16 · 5 obs

○ 2015-12-11 23:36:46
● 2016-06-26 15:44:26
● 2017-02-16 07:36:54
○ 2026-07-01 20:11:04
○ 2026-07-01 20:11:06

●A185.230.63.1072026-07-01 → 2026-07-01 · 3 obs

○ 2017-02-16 07:36:54
● 2026-07-01 20:11:04
● 2026-07-01 20:11:06

○A2607:f0d0:1003:8d:11::12015-08-13 → 2015-12-11 · 4 obs

● 2015-08-13 08:10:22
● 2015-12-11 23:36:46
○ 2016-06-26 15:44:26
○ 2026-07-01 20:11:06

○A2607:f0d0:1003:8d:13::12016-06-26 → 2017-02-16 · 5 obs

○ 2015-12-11 23:36:46
● 2016-06-26 15:44:26
● 2017-02-16 07:36:54
○ 2026-07-01 20:11:04
○ 2026-07-01 20:11:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
br	a.dns.br, b.dns.br, c.dns.br, d.dns.br...	-
bytelecom.com.br	ns2.task.com.br, ns1.task.com.br, ns4.task.com.br, ns3.task.com.br	8 records

✅ Authoritative Response

Server:169.61.160.3

NS records: ns2.task.com.br, ns1.task.com.br, ns4.task.com.br, ns3.task.com.br

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bytelecom.com.br (unsigned zone)

⏱️ Timing

Total: 598ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.230.63.107`
NS	4	`ns1.task.com.br, ns4.task.com.br...`
MX	2	`mx2.task.com.br (pri: 1), mx4.task.com.br (pri: 100)`
TXT	1	`v=spf1 mx a:smtp.task.com.br include:tas`
SOA	1	`ns1.task.com.br marcus.task.com.br`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns4.task.com.br, ns3.task.com.br, ns2.task.com.br...)

Analysis

IP Addresses

bytelecom.com.br has exactly one IP address — 185.230.63.107.

invasmart.com, stonypointib.com, acendaumavela.com.br plus two other host names have IP numbers in common with bytelecom.com.br.

Name Servers

Four name servers handle the delegation for bytelecom.com.br: ns1.task.com.br, ns2.task.com.br, ns3.task.com.br and ns4.task.com.br.

bytelecom.com.br partially shares its NS delegation with several other domains, including snceventos.com.br, g3engenharia.com.br, etiam.com.br and two others.

ns1.task.com.br, ns2.task.com.br, ns3.task.com.br and ns4.task.com.br each carry two IP addresses. ns1.task.com.br has 200.162.176.13 and 2804:4f0::13; ns2.task.com.br has 169.61.136.60 and 2607:f0d0:1f01:41::4; ns3.task.com.br has 169.61.160.3 and 2607:f0d0:1f01:41::3; ns4.task.com.br has 104.131.19.139 and 2604:a880:800:10::d1:5001.

Mail Servers

bytelecom.com.br uses two mail servers, mx2.task.com.br and mx4.task.com.br.

The mail server setup of bytelecom.com.br matches that of other domains such as 7solutions.com.br, vetornet.com.br, ortolife.com.br and two others.

At least some of the mail servers used by bytelecom.com.br are shared with other domains: belousa.com, frimaq.com.br, weblawyer.com.br and two others among them.

The mail servers mx1.task.com.br and mx3.task.com.br regularly co-occur with these mail servers.

Hosts with 6 IP addresses each:

mx2.task.com.br points to 177.93.104.137, 177.93.104.141, 177.93.104.145 and 3 other IP addresses.

mx4.task.com.br points to 177.93.104.137, 177.93.104.141, 177.93.104.145 and 3 other IP addresses.

The host names mx2.task.com.br and mx4.task.com.br both resolve to 177.93.104.137 IP addresses.

The host names mx2.task.com.br and mx4.task.com.br both resolve to 177.93.104.141 IP addresses.

The host names mx2.task.com.br and mx4.task.com.br both resolve to 177.93.104.145 IP addresses.

The host names mx2.task.com.br and mx4.task.com.br both resolve to 177.93.104.149 IP addresses.

The host names mx2.task.com.br and mx4.task.com.br both resolve to 177.93.104.153 IP addresses.

The host names mx2.task.com.br and mx4.task.com.br both resolve to 177.93.104.157 IP addresses.