cloudye.com - robtex.com
cloudye.com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783519017 | ||||||
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.netnstld@verisign-grs.com serial=1784824677 | ||||||
Same first word
cloudye.com |
Similar names
cloudey.net |
leyoucd.com |
eycloud.com |
yulcode.com |
yecloud.net |
dolycue.com |
ecloudy.net |
cuyoled.com.ar |
cloudey.com |
lyceudo.wixsite.com |
eycloud.net |
ecloudy.com |
ecloudy.eu |
cloudey.io |
DNS History
16 records (4 active, 12 former)
○NSdns1.name-services.com2015-07-24 → 2017-04-06 · 4 obs
● 2015-07-24 14:11:54
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
○NSdns2.name-services.com2015-07-24 → 2017-04-06 · 4 obs
● 2015-07-24 14:11:54
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
○NSdns3.name-services.com2015-07-24 → 2017-04-06 · 4 obs
● 2015-07-24 14:11:54
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
○NSdns4.name-services.com2015-07-24 → 2017-04-06 · 4 obs
● 2015-07-24 14:11:54
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
○NSdns5.name-services.com2015-07-24 → 2017-04-06 · 4 obs
● 2015-07-24 14:11:54
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
●NSlaunch1.spaceship.net2026-03-16 → 2026-07-23 · 3 obs
○ 2026-02-26 14:36:52
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
●NSlaunch2.spaceship.net2026-03-16 → 2026-07-23 · 3 obs
○ 2026-02-26 14:36:52
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
○NSns1.afternic.com2026-02-26 → 2026-02-26 · 4 obs
○ 2017-04-06 23:14:36
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
○NSns2.afternic.com2026-02-26 → 2026-02-26 · 4 obs
○ 2017-04-06 23:14:36
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
○MX.2026-02-26 → 2026-07-23 · 2 obs
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
○ 2026-07-23 16:57:16
○A101.227.182.352015-07-24 → 2016-02-06 · 4 obs
● 2015-07-24 14:11:54
● 2016-02-06 23:15:08
○ 2016-07-01 08:48:36
○ 2026-07-23 16:57:16
● 2016-02-06 23:15:08
○ 2016-07-01 08:48:36
○ 2026-07-23 16:57:16
○A13.248.169.482026-02-26 → 2026-02-26 · 4 obs
○ 2017-04-06 23:14:36
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
●A44.232.173.2492026-03-16 → 2026-07-23 · 3 obs
○ 2026-02-26 14:36:52
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
●A52.40.42.1132026-03-16 → 2026-07-23 · 3 obs
○ 2026-02-26 14:36:52
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
● 2026-03-16 10:20:54
● 2026-07-23 16:57:16
○A69.64.147.2432016-07-01 → 2017-04-06 · 5 obs
○ 2016-02-06 23:15:08
● 2016-07-01 08:48:36
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
● 2016-07-01 08:48:36
● 2017-04-06 23:14:36
○ 2026-02-26 14:36:52
○ 2026-07-23 16:57:16
○A76.223.54.1462026-02-26 → 2026-02-26 · 4 obs
○ 2017-04-06 23:14:36
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
● 2026-02-26 14:36:52
○ 2026-03-16 10:20:54
○ 2026-07-23 16:57:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| cloudye.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 685ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
cloudye.com points to the IP addresses 44.232.173.249 and 52.40.42.113
Additional host names — rajasthan.one, gittags.com, box.today and two others — share IP numbers with cloudye.com.
Name Servers
The NS records for cloudye.com delegate to launch1.spaceship.net and launch2.spaceship.net.
cloudye.com shares its name server setup with other domains, including skylinetrack.com, p2-p.com, yxc222.com and two others.
cloudye.com and other domains like keedis.com share at least a portion of their name servers.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.