cams.dev - dns.ninja
cams.dev
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
DNS History
10 records (8 active, 2 former)
●MXalt1.aspmx.l.google.com2026-02-21 → 2026-07-27 · 3 obs
● 2026-02-21 10:58:30
● 2026-07-27 08:26:22
●MXalt2.aspmx.l.google.com2026-02-21 → 2026-07-27 · 3 obs
● 2026-02-21 10:58:30
● 2026-07-27 08:26:22
●MXalt3.aspmx.l.google.com2026-02-21 → 2026-07-27 · 3 obs
● 2026-02-21 10:58:30
● 2026-07-27 08:26:22
●MXalt4.aspmx.l.google.com2026-02-21 → 2026-07-27 · 3 obs
● 2026-02-21 10:58:30
● 2026-07-27 08:26:22
●MXaspmx.l.google.com2026-02-21 → 2026-07-27 · 3 obs
● 2026-02-21 10:58:30
● 2026-07-27 08:26:22
○MXyour-dns-needs-immediate-attention.dev2017-01-02 → 2017-04-30 · 4 obs
● 2017-04-30 17:51:56
○ 2026-02-21 10:58:30
○ 2026-07-27 08:26:22
○A127.0.53.532017-01-02 → 2017-04-30 · 4 obs
● 2017-04-30 17:51:56
○ 2026-02-21 10:58:30
○ 2026-07-27 08:26:22
●A210.246.186.322026-02-21 → 2026-07-27 · 6 obs
● 2026-02-21 10:58:30
● 2026-04-03 12:03:28
○ 2026-04-06 09:44:00
● 2026-04-13 04:04:36
● 2026-07-27 08:26:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | 10 records |
| cams.dev | kiki.bunny.net, coco.bunny.net | - |
✅ Authoritative Response
Server:91.200.176.1
NS records: kiki.bunny.net, coco.bunny.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cams.dev (unsigned zone)
⏱️ Timing
Total: 648ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 210.246.186.32 |
| NS | 2 | kiki.bunny.net, coco.bunny.net |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=I1qC_GYcIBVyJqC |
| SOA | 1 | kiki.bunny.net hostmaster.bunny.net |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
cams.dev directs to one IP number, which is 210.246.186.32.
Name Servers
cams.dev uses two name servers for its delegation: coco.bunny.net and kiki.bunny.net.
cams.dev has the same name server delegation as a number of other domains, such as ocad3e.fr, villadesta.com.au, divendo.it and two more.
At least some of cams.dev's name servers are shared with other domains, for example machinelux.com, perfittraining.com, grandbeacon.com and two more.
These name servers are often deployed together with the name servers buy-domain.brandsly.com, for-sale.brandsly.com, ns1.domainvisitor.com and ns2.domainvisitor.com.
The two host names coco.bunny.net and kiki.bunny.net each have a pair of IP addresses: coco.bunny.net has 109.104.147.1 and 2400:52e0:fff2::1, and kiki.bunny.net has 91.200.176.1 and 2400:52e0:fff0::1.
Mail Servers
cams.dev has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
cams.dev shares at least some of its mail servers with other domains — for example ns500754.ns500742.ns500742.ns500731.ns500731.ns500731.ns500688.ns500671.ns500291.lustychickser.com, ns500734.ns500693.ns500693.ns500693.ns500734.ns500588.ns500693.ns500693.ns500693.ns500632.ns500632.ns500632.ns500632.ns500110.dtrkdll.com, northernsteppe.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.