kickbits.com - dns.ninja
kickbits.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=1783926842 | ||||||
Subdomains
Same first word
kickbits.com |
DNS History
12 records (10 active, 2 former)
●NSns1.kickbits.com2015-08-13 → 2026-07-13 · 2 obs
● 2026-07-13 07:18:42
●NSns1.mysecurecloudhost.com2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 10:39:22
● 2026-07-13 07:18:42
●NSns2.kickbits.com2015-08-13 → 2026-07-13 · 2 obs
● 2026-07-13 07:18:42
●NSns2.mysecurecloudhost.com2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 10:39:22
● 2026-07-13 07:18:42
●NSns3.mysecurecloudhost.com2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 10:39:22
● 2026-07-13 07:18:42
●NSns4.mysecurecloudhost.com2026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 10:39:22
● 2026-07-13 07:18:42
●MXalt1.aspmx.l.google.com2015-08-13 → 2026-07-13 · 2 obs
● 2026-07-13 07:18:42
●MXalt2.aspmx.l.google.com2015-08-13 → 2026-07-13 · 2 obs
● 2026-07-13 07:18:42
●MXaspmx.l.google.com2015-08-13 → 2026-07-13 · 2 obs
● 2026-07-13 07:18:42
○A170.39.77.1222026-03-26 → 2026-07-13 · 2 obs
○ 2026-07-13 07:18:42
●A194.39.148.672026-03-26 → 2026-07-13 · 3 obs
● 2026-03-26 10:39:22
● 2026-07-13 07:18:42
○A64.37.53.2462015-08-13 → 2017-06-21 · 4 obs
● 2017-06-21 20:01:40
○ 2026-03-26 10:39:22
○ 2026-07-13 07:18:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net... | - |
| kickbits.com | ns2.kickbits.com, ns1.kickbits.com | 2 records |
✅ Authoritative Response
Server:13.248.158.180
NS records: ns2.kickbits.com, ns1.kickbits.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for kickbits.com (unsigned zone)
⏱️ Timing
Total: 156ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 194.39.148.67 |
| NS | 4 | ns2.mysecurecloudhost.com, ns1.mysecurecloudhost.com... |
| MX | 3 | aspmx.l.google.com (pri: 0), alt2.aspmx.l.google.com (pri: 0)... |
| TXT | 1 | v=spf1 ip4:194.39.148.67 include:spf.mys |
| SOA | 1 | ns1.mysecurecloudhost.com servers.mysecu |
📌 Glue Records Collected
Total: 2
In-bailiwick: 2 (ns2.kickbits.com, ns1.kickbits.com)
Analysis
Hierarchy
The parent domain of ns1.kickbits.com and ns2.kickbits.com is kickbits.com.
IP Addresses
kickbits.com directs to one IP number, which is 194.39.148.67.
Host names such as d15778.usc1.stableserver.net and server.awsm.in share IP numbers with kickbits.com.
Name Servers
The DNS delegation for kickbits.com covers 6 name servers: ns1.kickbits.com, ns2.kickbits.com, ns1.mysecurecloudhost.com and 3 more.
kickbits.com shares at least some of its name servers with other domains, including 173.92.190.in-addr.arpa, human-group.mx, vignoblepremont.com and two others.
These name servers are frequently paired with the name servers ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com.
Hosts that resolve to one IP address:
ns1.kickbits.com points to the IP address 38.107.221.146.
ns2.kickbits.com points to the IP address 38.107.221.146.
ns1.mysecurecloudhost.com points to the IP address 13.248.158.180.
ns2.mysecurecloudhost.com points to the IP address 75.2.118.134.
ns3.mysecurecloudhost.com points to the IP address 76.223.26.245.
ns4.mysecurecloudhost.com points to the IP address 99.83.147.209.
These two host names — ns1.kickbits.com and ns2.kickbits.com — each point to 38.107.221.146 IP addresses.
Mail Servers
kickbits.com is handled by three mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
kickbits.com shares at least some of its mail servers with other domains — for example ns500759.ns500758.ns500698.ns500736.ns500698.ns500735.ns500735.ns500698.ns500698.ns500735.ns500708.ns500698.ns500619.ns500576.ns500576.trackreceptor.com, ns500742.ns500742.ns500742.ns500671.ns500742.ns500742.ns500671.ns500705.ns500705.ns500649.ns500291.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500699.ns500699.ns500693.ns500734.ns500693.ns500699.ns500734.ns500699.ns500588.ns500588.ns500699.ns500693.ns500699.ns500588.ns500612.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
aspmx.l.google.com resolves to 142.251.16.26 and 2607:f8b0:4004:c07::1b. alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a. alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a. All three hostnames point to two IP numbers each.