jacks.mitc.cloud - dns.ninja
jacks.mitc.cloud
| CNAME | central103.servers.mitc.cloud | ||||||
| CNAME | central103.centralus.cloudapp.azure.com | ||||||
| DNSSEC | ⚠️ Not signed | ||||||
| A | 172.173.115.101🇺🇸 Microsoft172.160.0.0/11 | ||||||
mitc.cloud
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-38.azure-dns.com ⭐ | ||||||
| NS | ns2-38.azure-dns.net | ||||||
| NS | ns3-38.azure-dns.org | ||||||
| NS | ns4-38.azure-dns.info | ||||||
| MX | logical-mx.email-protect.gosecure.net ⭐ | ||||||
| TXT | v=spf1 include:spf.protection.outlook.com ip4:209.23.125.128/26 ip4:209.23.11... | ||||||
| TXT | google-site-verification=tWjujljfBxN-Nc6dWxNtkZT_pcTFdEoBcLZ5QubRrow | ||||||
| TXT | MS=ms80985010 | ||||||
| TXT | ms-domain-verification=9fda1c8d-7137-48a0-8aac-115bde3d0e7a | ||||||
| SOA | ns1-38.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
●CNAMEcentral103.servers.mitc.cloud2026-02-17 → 2026-08-02 · 2 obs
● 2026-02-17 08:07:50
● 2026-08-02 23:58:54
● 2026-08-02 23:58:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.net, ns10.trs-dns.info, ns01.trs-dns.com, ns10.trs-dns.org | - |
| mitc.cloud | ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns3-38.azure-dns.org, ns4-38.azure-dns.info | - |
✅ Authoritative Response
Server:150.171.10.38
NS records: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns3-38.azure-dns.org, ns4-38.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mitc.cloud (unsigned zone)
⏱️ Timing
Total: 262ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | central103.servers.mitc.cloud |
Analysis
IP Addresses
jacks.mitc.cloud resolves to just one IP address, 172.173.115.101.
Other host names share IP numbers with jacks.mitc.cloud; central103.centralus.cloudapp.azure.com is one such example.