keyrus.cloud - robtex.com
Search for stuff
keyrus.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=1770456046 | ||||||
Up
git.keyrus.cloud |
Same first word
Similar names
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.info, ns10.trs-dns.org | 8 records |
| keyrus.cloud | ns-1326.awsdns-37.org, ns-42.awsdns-05.com, ns-1017.awsdns-63.net, ns-1832.awsdns-37.co.uk | - |
✅ Authoritative Response
Server: 205.251.192.42
NS records: ns-1326.awsdns-37.org, ns-42.awsdns-05.com, ns-1017.awsdns-63.net, ns-1832.awsdns-37.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for keyrus.cloud (unsigned zone)
⏱️ Timing
Total: 449ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 151.101.1.195, 151.101.65.195 |
| NS | 4 | ns-1017.awsdns-63.net, ns-1326.awsdns-37.org... |
| MX | 1 | inbound-smtp.us-east-1.amazonaws.com (pr |
| TXT | 1 | google-site-verification=C2lgwJqZo32QnT0 |
| SOA | 1 | ns-1832.awsdns-37.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.info...)
AI analysis
The parent of git.keyrus.cloud is keyrus.cloud.
Two IP numbers are pointed to by keyrus.cloud: 151.101.1.195 and 151.101.65.195.
other host names include divshot.com, www.playouter.net, colorleap.app, notestring.com and massageclick.com; they share IP numbers with keyrus.cloud.
keyrus.cloud delegates to four name servers: ns-42.awsdns-05.com, ns-1017.awsdns-63.net, ns-1326.awsdns-37.org and ns-1832.awsdns-37.co.uk.
keyrus.cloud at least partially shares name servers with other domains, for instance toflyers.org, magnushealthportal.net, helborg.fi, curecancer.eu and corntosschallenge.org.
these name servers are commonly used with ns-918.awsdns-50.net, ns-375.awsdns-46.com, ns-1030.awsdns-00.org, ns-1739.awsdns-25.co.uk, ns-1175.awsdns-18.org, ns-1580.awsdns-05.co.uk, ns-157.awsdns-19.com, ns-1127.awsdns-12.org, ns-1746.awsdns-26.co.uk and ns-941.awsdns-53.net.
Host names with two IP numbers: ns-42.awsdns-05.com points to 2600:9000:5300:2a00::1 and 205.251.192.42; ns-1017.awsdns-63.net points to 2600:9000:5303:f900::1 and 205.251.195.249; ns-1326.awsdns-37.org points to 2600:9000:5305:2e00::1 and 205.251.197.46; ns-1832.awsdns-37.co.uk points to 2600:9000:5307:2800::1 and 205.251.199.40.
keyrus.cloud is handled by a single mail server, inbound-smtp.us-east-1.amazonaws.com.
keyrus.cloud uses the same mail server setup as other domains, for instance kehanw.com, yuzu.com.whoisprivacyservice.org, news.elo7.com.br, sysupdateservice.com and autcomm.com.
keyrus.cloud shares at least partially some mail servers with other domains, for instance icedqsoft.atlassian.net, rbrand003.atlassian.net, 52ppt.com, thailife.com and brikit.atlassian.net.
Mail servers frequently appear alongside inbound-smtp.us-west-2.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
inbound-smtp.us-east-1.amazonaws.com resolves to five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32, 54.164.173.191 and 54.197.5.236.