managedrooms.com - dns.ninja
managedrooms.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=1785650122 | ||||||
Same first word
managedrooms.com |
managedrooms.net |
Similar names
DNS History
11 records (11 active, 0 former)
●NSns1-03.azure-dns.com2019-12-16 → 2026-08-02 · 2 obs
● 2026-08-02 06:14:36
●NSns2-03.azure-dns.net2019-12-16 → 2026-08-02 · 2 obs
● 2026-08-02 06:14:36
●NSns3-03.azure-dns.org2019-12-16 → 2026-08-02 · 2 obs
● 2026-08-02 06:14:36
●NSns4-03.azure-dns.info2019-12-16 → 2026-08-02 · 2 obs
● 2026-08-02 06:14:36
●A104.215.95.1872019-12-16 → 2026-08-02 · 2 obs
● 2026-08-02 06:14:36
●A20.112.250.1332026-02-28 → 2026-08-02 · 3 obs
● 2026-02-28 17:39:40
● 2026-08-02 06:14:36
●A20.231.239.2462026-02-28 → 2026-08-02 · 3 obs
● 2026-02-28 17:39:40
● 2026-08-02 06:14:36
●A20.236.44.1622026-02-28 → 2026-08-02 · 3 obs
● 2026-02-28 17:39:40
● 2026-08-02 06:14:36
●A20.70.246.202026-02-28 → 2026-08-02 · 3 obs
● 2026-02-28 17:39:40
● 2026-08-02 06:14:36
●A20.76.201.1712026-02-28 → 2026-08-02 · 3 obs
● 2026-02-28 17:39:40
● 2026-08-02 06:14:36
●A52.164.206.562019-12-16 → 2026-08-02 · 2 obs
● 2026-08-02 06:14:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| managedrooms.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:208.84.5.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 managedrooms.com (unsigned zone)
⏱️ Timing
Total: 171ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 7 | 104.215.95.187, 52.164.206.56... |
| NS | 4 | ns1-03.azure-dns.com, ns2-03.azure-dns.net... |
| TXT | 1 | v=DMARC1; p=reject; pct=100; rua=mailto: |
| 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
IP Addresses
managedrooms.com points to 7 IP addresses, including 20.70.246.20, 20.76.201.171 and 20.112.250.133, plus 4 other.
restart-europe.net, hotmail-msn.org, fusionfrenzy.net plus two other host names have IP numbers in common with managedrooms.com.
Name Servers
Four name servers handle the delegation for managedrooms.com: ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.
There is at least partial name server overlap between managedrooms.com and other domains — cbvfd.net, microsoftsurface.gr, howrse.pl and two more among them.
These name servers frequently co-occur with the name servers ns2.if.fi and ns4.if.fi.
All four hostnames — ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org — resolve to two IP numbers apiece: ns1-03.azure-dns.com to 13.107.236.3 and 2603:1061:0:700::3; ns4-03.azure-dns.info to 208.84.5.3 and 2620:1ec:bda:700::3; ns2-03.azure-dns.net to 150.171.21.3 and 2620:1ec:8ec:700::3; ns3-03.azure-dns.org to 204.14.183.3 and 2a01:111:4000:700::3.