cyclefile.com - dns.ninja
cyclefile.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=1780942951 | ||||||
Same first word
cyclefile.com |
Similar names
DNS History
11 records (9 active, 2 former)
●NSns23.domaincontrol.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●NSns24.domaincontrol.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●MXalt1.aspmx.l.google.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●MXalt2.aspmx.l.google.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●MXaspmx.l.google.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●MXaspmx2.googlemail.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●MXaspmx3.googlemail.com2015-05-27 → 2026-06-08 · 2 obs
● 2026-06-08 18:46:20
●A15.197.225.1282026-02-26 → 2026-06-08 · 3 obs
● 2026-02-26 16:45:20
● 2026-06-08 18:46:20
○A184.168.183.12015-05-27 → 2016-01-03 · 4 obs
● 2016-01-03 04:16:12
○ 2016-05-07 13:06:34
○ 2026-06-08 18:46:20
●A3.33.251.1682026-02-26 → 2026-06-08 · 3 obs
● 2026-02-26 16:45:20
● 2026-06-08 18:46:20
○A50.63.202.472016-05-07 → 2018-08-11 · 5 obs
● 2016-05-07 13:06:34
● 2018-08-11 07:19:38
○ 2026-02-26 16:45:20
○ 2026-06-08 18:46:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net... | - |
| cyclefile.com | ns23.domaincontrol.com, ns24.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.101.12
NS records: ns23.domaincontrol.com, ns24.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cyclefile.com (unsigned zone)
⏱️ Timing
Total: 282ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns23.domaincontrol.com, ns24.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| TXT | 3 | google-site-verification=pWWnJxT8oHmBLkT, google-site-verification=zsdrtw9Qb_4Mj8u... |
| SOA | 1 | ns23.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns23.domaincontrol.com, ns23.domaincontrol.com, ns24.domaincontrol.com...)
Analysis
IP Addresses
cyclefile.com points to two IP numbers: 3.33.251.168 and 15.197.225.128.
Among the host names that share IP numbers with cyclefile.com are compraires.com, anotheruse.com, ebvl.com and two others.
Name Servers
cyclefile.com uses two name servers for its delegation: ns23.domaincontrol.com and ns24.domaincontrol.com.
cyclefile.com has the same name server delegation as a number of other domains, such as sentryac.com, slicedrop.org, konacart.com and two more.
At least some of cyclefile.com's name servers are also used by other domains, among them fortmorrowfire.com.
The two host names ns23.domaincontrol.com and ns24.domaincontrol.com each have a pair of IP addresses: ns23.domaincontrol.com has 97.74.101.12 and 2603:5:2151::c, and ns24.domaincontrol.com has 173.201.69.12 and 2603:5:2251::c.
Mail Servers
cyclefile.com uses 5 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com plus two additional ones.
cyclefile.com shares at least some of its mail servers with other domains — for example tnt.pl, ns500754.ns500671.ns500671.ns500731.ns500671.ns500731.ns500754.ns500704.ns500688.ns500688.ns500704.ns500649.ns500291.ns500131.lustychickser.com, dkentertainment.vn and two more.
These mail servers tend to co-occur with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and three additional mail servers.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.