cyberram.com - robtex.com
cyberram.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=1776058567 | ||||||
Subdomains
www.cyberram.com |
Same first word
cyberram.com |
Similar names
DNS History
18 records (5 active, 13 former)
○NSdns10.parkpage.foundationapi.com2017-02-09 → 2017-02-09 · 4 obs
● 2017-02-09 22:37:10
○ 2019-12-26 07:23:14
○ 2026-04-13 05:52:44
○NSdns7.parkpage.foundationapi.com2016-02-09 → 2016-02-09 · 4 obs
● 2016-02-09 16:19:18
○ 2016-05-04 22:42:42
○ 2026-04-13 05:52:44
○NSdns8.parkpage.foundationapi.com2016-02-09 → 2016-02-09 · 4 obs
● 2016-02-09 16:19:18
○ 2016-05-04 22:42:42
○ 2026-04-13 05:52:44
○NSdns9.parkpage.foundationapi.com2017-02-09 → 2017-02-09 · 4 obs
● 2017-02-09 22:37:10
○ 2019-12-26 07:23:14
○ 2026-04-13 05:52:44
●NSns1.name.com2026-03-27 → 2026-04-13 · 3 obs
● 2026-03-27 01:13:14
● 2026-04-13 05:52:44
○NSns1.yourhostingaccount.com2015-06-03 → 2016-05-04 · 6 obs
● 2015-11-10 13:06:30
○ 2016-02-09 16:19:18
● 2016-05-04 22:42:42
○ 2017-02-09 22:37:10
○ 2026-04-13 05:52:44
●NSns1kwy.name.com2026-03-27 → 2026-04-13 · 3 obs
● 2026-03-27 01:13:14
● 2026-04-13 05:52:44
○NSns2.yourhostingaccount.com2015-06-03 → 2016-05-04 · 6 obs
● 2015-11-10 13:06:30
○ 2016-02-09 16:19:18
● 2016-05-04 22:42:42
○ 2017-02-09 22:37:10
○ 2026-04-13 05:52:44
○NSns29.domaincontrol.com2019-12-26 → 2019-12-26 · 4 obs
● 2019-12-26 07:23:14
○ 2026-03-27 01:13:14
○ 2026-04-13 05:52:44
●NSns2kry.name.com2026-03-27 → 2026-04-13 · 3 obs
● 2026-03-27 01:13:14
● 2026-04-13 05:52:44
○NSns30.domaincontrol.com2019-12-26 → 2019-12-26 · 4 obs
● 2019-12-26 07:23:14
○ 2026-03-27 01:13:14
○ 2026-04-13 05:52:44
●NSns3bfm.name.com2026-03-27 → 2026-04-13 · 3 obs
● 2026-03-27 01:13:14
● 2026-04-13 05:52:44
●NSns4htz.name.com2026-03-27 → 2026-04-13 · 3 obs
● 2026-03-27 01:13:14
● 2026-04-13 05:52:44
○A141.8.225.2372015-06-03 → 2016-05-04 · 6 obs
● 2015-11-10 13:06:30
○ 2016-02-09 16:19:18
● 2016-05-04 22:42:42
○ 2017-02-09 22:37:10
○ 2026-04-13 05:52:44
○A184.168.131.2412019-12-26 → 2019-12-26 · 4 obs
● 2019-12-26 07:23:14
○ 2026-03-27 01:13:14
○ 2026-04-13 05:52:44
○A209.99.40.2212016-02-09 → 2016-02-09 · 4 obs
● 2016-02-09 16:19:18
○ 2016-05-04 22:42:42
○ 2026-04-13 05:52:44
○A209.99.40.2222017-02-09 → 2017-02-09 · 4 obs
● 2017-02-09 22:37:10
○ 2019-12-26 07:23:14
○ 2026-04-13 05:52:44
○PTRdns9.parkpage.foundationapi.com2017-02-09 → 2017-02-09 · 3 obs
○ 2019-12-26 07:23:14
○ 2026-04-13 05:52:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| cyberram.com | ns1kwy.name.com, ns2kry.name.com, ns3bfm.name.com, ns4htz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1kwy.name.com, ns2kry.name.com, ns3bfm.name.com, ns4htz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cyberram.com (unsigned zone)
⏱️ Timing
Total: 109ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1kwy.name.com, ns2kry.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1kwy.name.com, ns1kwy.name.com, ns2kry.name.com...)
Analysis
Hierarchy
cyberram.com is the parent of www.cyberram.com.
Name Servers
cyberram.com delegates to five name servers: ns1.name.com, ns1kwy.name.com, ns2kry.name.com, ns3bfm.name.com and ns4htz.name.com.
cyberram.com shares some name servers with other domains, for example betjumanji.com, clydemandelin.com, ontolawgy.com, anunciomex.com and strategyai.consulting.
these name servers are often used with ns1kpv.name.com, ns3jmt.name.com, ns4dmx.name.com, ns4lpv.name.com, ns1cnb.name.com, ns3cna.name.com, ns1dns.name.com, ns2fln.name.com, ns1djs.name.com and ns2bls.name.com.
Host names with two IP numbers:
ns1.name.com points to 2a00:edc0:107::1 and 163.114.216.17
ns1kwy.name.com points to 2a00:edc0:107::1 and 163.114.216.17
ns2kry.name.com points to 2402:cf80:107::1 and 163.114.216.49
ns3bfm.name.com points to 2a00:edc0:107::49 and 163.114.217.17
ns4htz.name.com points to 2402:cf80:107::49 and 163.114.217.49
Host names pointing to 2a00:edc0:107::1: ns1.name.com and ns1kwy.name.com
Host names pointing to 163.114.216.17: ns1.name.com and ns1kwy.name.com