cloud-idf.com - dns.ninja
cloud-idf.com
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=1784964387 | ||||||
PTR for
Subdomains
www.cloud-idf.com |
100148adapter.cloud-idf.com |
Same first word
cloud-idf.com |
DNS History
22 records (17 active, 5 former)
○NSns-14.dns.jp-e1.cloudn-service.com2016-12-17 → 2018-08-07 · 4 obs
● 2018-08-07 06:40:48
○ 2026-04-02 18:27:48
○ 2026-07-25 07:33:20
○NSns-15.dns.jp-e1.cloudn-service.com2016-12-17 → 2018-08-07 · 4 obs
● 2018-08-07 06:40:48
○ 2026-04-02 18:27:48
○ 2026-07-25 07:33:20
○NSns-16.dns.jp-e1.cloudn-service.com2016-12-17 → 2018-08-07 · 4 obs
● 2018-08-07 06:40:48
○ 2026-04-02 18:27:48
○ 2026-07-25 07:33:20
●NSns1-03.azure-dns.com2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●NSns2-03.azure-dns.net2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●NSns3-03.azure-dns.org2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●NSns4-03.azure-dns.info2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●MXalt1.aspmx.l.google.com2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●MXalt2.aspmx.l.google.com2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●MXalt3.aspmx.l.google.com2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●MXalt4.aspmx.l.google.com2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
●MXaspmx.l.google.com2026-04-02 → 2026-07-25 · 3 obs
● 2026-04-02 18:27:48
● 2026-07-25 07:33:20
○MXvcgw1.ocn.ad.jp2016-12-17 → 2018-08-07 · 4 obs
● 2018-08-07 06:40:48
○ 2026-04-02 18:27:48
○ 2026-07-25 07:33:20
○MXvcgw2.ocn.ad.jp2016-12-17 → 2018-08-07 · 4 obs
● 2018-08-07 06:40:48
○ 2026-04-02 18:27:48
○ 2026-07-25 07:33:20
●A104.215.3.302026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A104.215.49.1262026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A104.215.55.952026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A104.215.6.2432026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A104.46.235.1842026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A20.222.31.2072026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A20.89.131.2132026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
●A40.74.92.2172026-04-02 → 2026-07-25 · 2 obs
● 2026-07-25 07:33:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net... | - |
| cloud-idf.com | ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info | 2 records |
✅ Authoritative Response
Server:204.14.183.3
NS records: ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cloud-idf.com (unsigned zone)
⏱️ Timing
Total: 418ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 8 | 40.74.92.217, 104.46.235.184... |
| NS | 4 | ns1-03.azure-dns.com, ns2-03.azure-dns.net... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 +ip4:40.74.92.217/32 +ip4:104.46. |
| SOA | 1 | ns1-03.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-03.azure-dns.com, ns1-03.azure-dns.com)
Analysis
Hierarchy
www.cloud-idf.com and 100148adapter.cloud-idf.com each fall under cloud-idf.com as their parent domain.
IP Addresses
cloud-idf.com directs to 8 IP numbers: 20.89.131.213, 20.222.31.207, 40.74.92.217 and 5 other.
Name Servers
The NS records for cloud-idf.com point to four name servers: ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.
cloud-idf.com has at least partial name server overlap with other domains, such as fairy.pl, economa.se, treasury4.com and two others.
ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org all point to exactly two IP numbers each: ns1-03.azure-dns.com → 13.107.236.3 and 2603:1061:0:700::3; ns4-03.azure-dns.info → 208.84.5.3 and 2620:1ec:bda:700::3; ns2-03.azure-dns.net → 150.171.21.3 and 2620:1ec:8ec:700::3; ns3-03.azure-dns.org → 204.14.183.3 and 2a01:111:4000:700::3.
Mail Servers
cloud-idf.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between cloud-idf.com and other domains, including fuerte.com, tagul.com, benvesta.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
The A records for aspmx.l.google.com return 192.179.18.26 and 2607:f8b0:4004:c23::1a.
The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1a.
The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.
The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1a.
The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1b.