getinsign.cloud - dns.ninja
getinsign.cloud
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1783054228 | ||||||
Same first word
getinsign.cloud |
getinsign.com |
getinsign.de |
Similar names
DNS History
5 records (5 active, 0 former)
●NSns-1039.awsdns-01.org2026-03-15 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:00
●NSns-115.awsdns-14.com2026-03-15 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:00
●NSns-1702.awsdns-20.co.uk2026-03-15 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:00
●NSns-595.awsdns-10.net2026-03-15 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:00
●MXbsisoftware-cloud0i.mail.protection.outlook.com2026-03-15 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| getinsign.cloud | ns-115.awsdns-14.com, ns-595.awsdns-10.net, ns-1039.awsdns-01.org, ns-1702.awsdns-20.co.uk | - |
✅ Authoritative Response
Server:205.251.198.166
NS records: ns-115.awsdns-14.com, ns-595.awsdns-10.net, ns-1039.awsdns-01.org, ns-1702.awsdns-20.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for getinsign.cloud (unsigned zone)
⏱️ Timing
Total: 433ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1039.awsdns-01.org, ns-115.awsdns-14.com... |
| MX | 1 | bsisoftware-cloud0i.mail.protection.outl |
| SOA | 1 | ns-115.awsdns-14.com awsdns-hostmaster.a |
Analysis
Name Servers
The authoritative name servers for getinsign.cloud are ns-115.awsdns-14.com, ns-595.awsdns-10.net, ns-1039.awsdns-01.org and ns-1702.awsdns-20.co.uk.
The name servers of getinsign.cloud overlap at least partially with those of other domains — among them d33udneyygq2v6.cloudfront.net, 127.22.3.in-addr.arpa, 46.222.18.in-addr.arpa and two more.
These name servers commonly co-occur with the name servers ns1-24-us-east-2.ec2-rdns.amazonaws.com, ns2-24-us-east-2.ec2-rdns.amazonaws.com, ns3-24-us-east-2.ec2-rdns.amazonaws.com and ns4-24-us-east-2.ec2-rdns.amazonaws.com.
Each of the four hosts ns-115.awsdns-14.com, ns-595.awsdns-10.net, ns-1039.awsdns-01.org and ns-1702.awsdns-20.co.uk has two IP addresses. ns-115.awsdns-14.com points to 205.251.192.115 and 2600:9000:5300:7300::1. ns-595.awsdns-10.net points to 205.251.194.83 and 2600:9000:5302:5300::1. ns-1039.awsdns-01.org points to 205.251.196.15 and 2600:9000:5304:f00::1. ns-1702.awsdns-20.co.uk points to 205.251.198.166 and 2600:9000:5306:a600::1.
Mail Servers
Mail for getinsign.cloud is handled by a single mail server, bsisoftware-cloud0i.mail.protection.outlook.com.
The mail server configuration of getinsign.cloud is identical to that of other domains — bsi-software.cloud being one example.
bsisoftware-cloud0i.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.185.12, 52.101.185.13, 52.101.185.14 and 5 others.