chasingbluesky.net - robtex.com
chasingbluesky.net
net
| 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=1778513691 | ||||||
Subdomains
assets.chasingbluesky.net |
Same first word
chasingbluesky.net |
DNS History
18 records (11 active, 7 former)
○NSns01.cashparking.com2015-05-28 → 2015-05-28 · 3 obs
○ 2015-10-26 02:00:22
○ 2026-05-11 15:56:12
●NSns1.name.com2026-04-07 → 2026-05-11 · 3 obs
● 2026-04-07 20:43:20
● 2026-05-11 15:56:12
○NSns1.snare.arvixe.com2016-08-09 → 2017-10-29 · 5 obs
● 2016-08-09 16:27:40
● 2017-10-29 20:23:26
○ 2026-04-07 20:43:20
○ 2026-05-11 15:56:12
●NSns1bcp.name.com2026-04-07 → 2026-05-11 · 3 obs
● 2026-04-07 20:43:20
● 2026-05-11 15:56:12
○NSns2.snare.arvixe.com2016-08-09 → 2017-10-29 · 5 obs
● 2016-08-09 16:27:40
● 2017-10-29 20:23:26
○ 2026-04-07 20:43:20
○ 2026-05-11 15:56:12
●NSns2bls.name.com2026-04-07 → 2026-05-11 · 3 obs
● 2026-04-07 20:43:20
● 2026-05-11 15:56:12
●NSns3cpr.name.com2026-04-07 → 2026-05-11 · 3 obs
● 2026-04-07 20:43:20
● 2026-05-11 15:56:12
●NSns4jnz.name.com2026-04-07 → 2026-05-11 · 3 obs
● 2026-04-07 20:43:20
● 2026-05-11 15:56:12
●MXalt1.aspmx.l.google.com2016-08-09 → 2026-05-11 · 3 obs
● 2016-08-09 16:27:40
● 2026-05-11 15:56:12
●MXalt2.aspmx.l.google.com2016-08-09 → 2026-05-11 · 3 obs
● 2016-08-09 16:27:40
● 2026-05-11 15:56:12
●MXalt3.aspmx.l.google.com2016-08-09 → 2026-05-11 · 3 obs
● 2016-08-09 16:27:40
● 2026-05-11 15:56:12
●MXalt4.aspmx.l.google.com2016-08-09 → 2026-05-11 · 3 obs
● 2016-08-09 16:27:40
● 2026-05-11 15:56:12
●MXaspmx.l.google.com2016-08-09 → 2026-05-11 · 3 obs
● 2016-08-09 16:27:40
● 2026-05-11 15:56:12
○MXmailstore1.secureserver.net2015-05-28 → 2015-05-28 · 3 obs
○ 2015-10-26 02:00:22
○ 2026-05-11 15:56:12
○MXsmtp.secureserver.net2015-05-28 → 2015-05-28 · 3 obs
○ 2015-10-26 02:00:22
○ 2026-05-11 15:56:12
●A143.198.70.802026-04-07 → 2026-05-11 · 3 obs
● 2026-04-07 20:43:20
● 2026-05-11 15:56:12
○A143.95.251.412016-08-09 → 2017-10-29 · 5 obs
● 2016-08-09 16:27:40
● 2017-10-29 20:23:26
○ 2026-04-07 20:43:20
○ 2026-05-11 15:56:12
○A184.168.221.962015-05-28 → 2015-05-28 · 3 obs
○ 2015-10-26 02:00:22
○ 2026-05-11 15:56:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | b.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, k.gtld-servers.net... | - |
| chasingbluesky.net | ns1bcp.name.com, ns2bls.name.com, ns3cpr.name.com, ns4jnz.name.com | - |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1bcp.name.com, ns2bls.name.com, ns3cpr.name.com, ns4jnz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for chasingbluesky.net (unsigned zone)
⏱️ Timing
Total: 873ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 143.198.70.80 |
| NS | 4 | ns1bcp.name.com, ns2bls.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=1f5IfgDjx8Zk_CA |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
Hierarchy
The parent of assets.chasingbluesky.net is chasingbluesky.net.
IP Addresses
chasingbluesky.net points to a single IP address: 143.198.70.80.
Other host names, such as onbecomingdeath.com and rassoft.com, share IP numbers with chasingbluesky.net.
Name Servers
chasingbluesky.net is delegated to five name servers: ns1.name.com, ns1bcp.name.com, ns2bls.name.com, ns3cpr.name.com and ns4jnz.name.com.
chasingbluesky.net at least partially shares name servers with other domains, for example chrismacdonaldselvis.com, hprutah.com, pdf-pdq.com, imbee.com and roboticsindc.com.
these name servers are commonly used with the following name servers: ns1hwy.name.com, ns1psw.name.com, ns1cnb.name.com, ns3cna.name.com, ns2fgp.name.com, ns3fqs.name.com, ns3fgh.name.com, ns1kwy.name.com, ns4hmp.name.com and ns1mtw.name.com.
Host names with two IP numbers:
ns1.name.com points to: 2a00:edc0:107::1 and 163.114.216.17
ns1bcp.name.com points to: 2a00:edc0:107::1 and 163.114.216.17
ns2bls.name.com points to: 2402:cf80:107::1 and 163.114.216.49
ns3cpr.name.com points to: 2a00:edc0:107::49 and 163.114.217.17
ns4jnz.name.com points to: 2402:cf80:107::49 and 163.114.217.49
Hosts pointing to 2a00:edc0:107::1: ns1.name.com and ns1bcp.name.com
Hosts pointing to 163.114.216.17: ns1.name.com and ns1bcp.name.com
Mail Servers
chasingbluesky.net is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
chasingbluesky.net shares at least partially some mail servers with other domains, for instance waimanwong.com, ns500699.ns500699.ns500693.ns500734.ns500734.ns500693.ns500588.ns500588.ns500612.ns500612.ns500588.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500768.ns500759.ns500698.ns500758.ns500759.ns500698.ns500736.ns500735.ns500698.ns500735.ns500698.ns500698.ns500686.ns500652.trackreceptor.com, ns500765.ns500699.ns500693.ns500699.ns500699.ns500699.ns500588.ns500588.ns500588.ns500588.ns500693.ns500588.ns500110.dtrkdll.com and alloapero.fr.
these mail servers are often used together with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers
Each host name points to two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4023:c0d::1b and 142.250.101.27
alt1.aspmx.l.google.com points to 2a00:1450:4025:402::1a and 192.178.213.26
alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1b and 172.253.116.26
alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1b and 192.178.223.27
alt4.aspmx.l.google.com points to 2607:f8b0:4003:c4a::1a and 142.251.96.27