`transportes.cloud`

DNSSEC	⚠️ Not signed
A	2606:4700:3034::6815:d49^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:9b0f^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.13.73^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.155.15^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`kim.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a7e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c07e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kim.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:207e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kim.ns.cloudflare.com`
		A	108.162.192.126^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	172.64.32.126^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	173.245.58.126^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
NS	`lloyd.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bc5^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lloyd.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1c5^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lloyd.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21c5^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lloyd.ns.cloudflare.com`
		A	108.162.193.197^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lloyd.ns.cloudflare.com`
		A	172.64.33.197^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lloyd.ns.cloudflare.com`
		A	173.245.59.197^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lloyd.ns.cloudflare.com`
MX	`mx2.zoho.com` ⭐
		A	136.143.183.44^{🇺🇸 ZohoAS136.143.182.0/23 Zoho}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx3.zoho.com`⁽²⁰⁾
		A	136.143.191.44^{🇺🇸 ZohoAS136.143.190.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
MX	`mx.zoho.com`⁽⁵⁰⁾
		A	136.143.183.44^{🇺🇸 ZohoAS136.143.182.0/23 Zoho}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
		A	136.143.191.44^{🇺🇸 ZohoAS136.143.190.0/23 Zoho Corporation}
			PTR	`mx2.zoho.com`
			PTR	`mx3.zoho.com`
			PTR	`mx.zoho.com`
			PTR	`mx2.zohomail.com`
			PTR	`mx3.zohomail.com`
			PTR	`mx.zohomail.com`
TXT	`v=spf1 include:zoho.com ~all`
TXT	`zoho-verification=zb81776807.zmverify.zoho.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.13.73, 172.67.155.15
		IPv6	2606:4700:3034::6815:d49, 2606:4700:3034::ac43:9b0f
SOA	`kim.ns.cloudflare.com`dns@cloudflare.com serial=2399966591

`cloud`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1774554933

Same first word

Similar names

DNS History

9 records (9 active, 0 former)

●NSkim.ns.cloudflare.com2026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●NSlloyd.ns.cloudflare.com2026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●MXmx.zoho.com2026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●MXmx2.zoho.com2026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●MXmx3.zoho.com2026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●A104.21.13.732026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●A172.67.155.152026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●A2606:4700:3034::6815:d492026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

●A2606:4700:3034::ac43:9b0f2026-03-26 → 2026-03-26 · 2 obs

● 2026-03-26 04:21:14
● 2026-03-26 20:21:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cloud	ns10.trs-dns.org, ns01.trs-dns.net, ns01.trs-dns.com, ns10.trs-dns.info	-
transportes.cloud	kim.ns.cloudflare.com, lloyd.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.126

NS records: kim.ns.cloudflare.com, lloyd.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for transportes.cloud (unsigned zone)

⏱️ Timing

Total: 490ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.13.73, 172.67.155.15`
AAAA	2	`2606:4700:3034::6815:d49, 2606:4700:3034::ac43:9b0f`
NS	2	`kim.ns.cloudflare.com, lloyd.ns.cloudflare.com`
MX	3	`mx.zoho.com (pri: 10), mx2.zoho.com (pri: 20)...`
TXT	2	`v=spf1 include:zoho.com ~all, zoho-verification=zb81776807.zmverify.zo`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`kim.ns.cloudflare.com dns.cloudflare.com`

Analysis

IP Addresses

transportes.cloud maps to four IP numbers: 2606:4700:3034::6815:d49, 2606:4700:3034::ac43:9b0f, 104.21.13.73 and 172.67.155.15.

Other host names, for instance pradenadeatienza.com, office365fax6.jenl1696.workers.dev, khushbooprints.com, office365fax4.jenl1696.workers.dev and www.universitiesandcolleges.org share IP numbers with transportes.cloud.

Name Servers

Two name servers kim.ns.cloudflare.com and lloyd.ns.cloudflare.com handle delegation for transportes.cloud.

transportes.cloud uses the same name server setup as other domains, for example filesmaclink.me, 360icalifornia.com, mxbokep.org, mapored.net and ecowonder.org.

transportes.cloud partially shares name servers with other domains; examples include planton.cn, telavivdeclick.com, bonaslot-2025.ink, yaohaoyao.cn and healthevolutionproject.com.

These name servers are commonly used with the name servers abby.ns.cloudflare.com, casey.ns.cloudflare.com, leif.ns.cloudflare.com, walt.ns.cloudflare.com and todd.ns.cloudflare.com.

Host names with six IP numbers: kim.ns.cloudflare.com points to: 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e, 108.162.192.126, 172.64.32.126 and 173.245.58.126; lloyd.ns.cloudflare.com points to: 2606:4700:58::adf5:3bc5, 2803:f800:50::6ca2:c1c5, 2a06:98c1:50::ac40:21c5, 108.162.193.197, 172.64.33.197 and 173.245.59.197.

Mail Servers

transportes.cloud is handled by three mail servers: mx2.zoho.com, mx3.zoho.com and mx.zoho.com.

transportes.cloud shares some mail servers with other domains, at least partially, such as dimakrasner.com, nse.org.ng, bx8.com, boluo.tw and satocolombia.com.

Host names with two IP numbers:

The host name mx.zoho.com points to: 136.143.183.44 and 136.143.191.44.

Host names with one IP number:

The host name mx2.zoho.com points to: 136.143.183.44.

The host name mx3.zoho.com points to: 136.143.191.44.

Host names that point to 136.143.183.44: mx.zoho.com and mx2.zoho.com.

Host names that point to 136.143.191.44: mx.zoho.com and mx3.zoho.com.

transportes.cloud - robtex.com