rolicloud.com - robtex.com
rolicloud.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=1786113684 | ||||||
Same first word
rolicloud.com |
Similar names
DNS History
5 records (5 active, 0 former)
βNSns1cnb.name.com2026-07-07 β 2026-08-07 Β· 2 obs
β 2026-08-07 14:51:00
βNSns2hjl.name.com2026-07-07 β 2026-08-07 Β· 2 obs
β 2026-08-07 14:51:00
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net... | - |
| rolicloud.com | ns2hjl.name.com, ns4cjp.name.com, ns3cna.name.com, ns1cnb.name.com | 8 records |
β Authoritative Response
Server:163.114.216.49
NS records: ns2hjl.name.com, ns4cjp.name.com, ns3cna.name.com, ns1cnb.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for rolicloud.com (unsigned zone)
β±οΈ Timing
Total: 1036ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns2hjl.name.com, ns4cjp.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns2hjl.name.com, ns2hjl.name.com, ns4cjp.name.com...)
Analysis
Name Servers
The authoritative name servers for rolicloud.com are ns1.name.com, ns1cnb.name.com, ns2hjl.name.com and two others.
There is at least partial name server overlap between rolicloud.com and other domains β pause-eg.com, dmcmn.org, gallant.in and two more among them.
These name servers regularly appear alongside ns3cna.name.com, ns4cjp.name.com, ns1kwy.name.com and 7 other name servers in NS record sets.
Hosts with two IP numbers each:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1cnb.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2hjl.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3cna.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4cjp.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1cnb.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1cnb.name.com each resolve to 163.114.216.17 IP addresses.