ledtek.com - dns.ninja
ledtek.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 45.33.82.87🇺🇸 AKAMAI-LINODE-AP45.33.64.0/19 Akamai Technologies | ||||||
| PTR | spro6.fcomet.com | ||||||
| NS | kevin.quicns.net ⭐ | ||||||
| A | 64.66.241.1🇺🇸 AS39836764.66.241.0/24 Proxy route object created by MICRON21-AU AS38880 | ||||||
| NS | jon.quicns.org | ||||||
| A | 64.66.240.1🇺🇸 AS39836764.66.240.0/24 Proxy route object created by MICRON21-AU AS38880 | ||||||
| TXT | MS=ms60786480 | ||||||
| TXT | google-site-verification=_8LvpSPw27CAS6ZlBaZdH2wyqXf-wbWFNgEYWBiEVd8 | ||||||
| SOA | kevin.quicns.netdns@quicns.com serial=1755874159 | ||||||
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=1786658574 | ||||||
Previously NS for
ledtek.com |
Subdomains
mail.ledtek.com |
Same first word
Similar names
DNS History
11 records (3 active, 8 former)
○NSdns1.51.net2015-06-24 → 2017-08-26 · 4 obs
● 2017-08-26 11:09:00
○ 2026-02-17 08:29:22
○ 2026-08-13 22:05:50
○NSdns2.51.net2015-06-24 → 2017-08-26 · 4 obs
● 2017-08-26 11:09:00
○ 2026-02-17 08:29:22
○ 2026-08-13 22:05:50
●NSjon.quicns.org2026-02-17 → 2026-08-13 · 3 obs
● 2026-02-17 08:29:22
● 2026-08-13 22:05:50
●NSkevin.quicns.net2026-02-17 → 2026-08-13 · 3 obs
● 2026-02-17 08:29:22
● 2026-08-13 22:05:50
○NSledtek.com2015-06-24 → 2017-08-26 · 4 obs
● 2017-08-26 11:09:00
○ 2026-02-17 08:29:22
○ 2026-08-13 22:05:50
○MXgmx130.cn4e.com2015-06-24 → 2026-02-17 · 4 obs
● 2026-02-17 08:29:22
○ 2026-03-08 14:34:48
○ 2026-08-13 22:05:50
○A43.240.29.662017-07-27 → 2017-08-26 · 5 obs
● 2017-07-27 19:27:52
● 2017-08-26 11:09:00
○ 2026-02-17 08:29:22
○ 2026-08-13 22:05:50
●A45.33.82.872026-02-17 → 2026-08-13 · 3 obs
● 2026-02-17 08:29:22
● 2026-08-13 22:05:50
○A71.18.24.1222017-06-27 → 2017-07-17 · 5 obs
● 2017-06-27 23:38:28
● 2017-07-17 09:59:14
○ 2017-07-27 19:27:52
○ 2026-08-13 22:05:50
○A71.18.33.1382016-10-17 → 2016-10-17 · 4 obs
● 2016-10-17 23:52:32
○ 2017-06-27 23:38:28
○ 2026-08-13 22:05:50
○A98.130.112.1642015-06-24 → 2016-03-05 · 4 obs
● 2016-03-05 00:49:42
○ 2016-10-17 23:52:32
○ 2026-08-13 22:05:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, g.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net... | - |
| ledtek.com | jon.quicns.org, kevin.quicns.net | - |
✅ Authoritative Response
Server:64.66.240.1
NS records: jon.quicns.org, kevin.quicns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ledtek.com (unsigned zone)
⏱️ Timing
Total: 302ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.33.82.87 |
| NS | 2 | kevin.quicns.net, jon.quicns.org |
| TXT | 2 | MS=ms60786480, google-site-verification=_8LvpSPw27CAS6Z |
| SOA | 1 | kevin.quicns.net dns.quicns.com |
Analysis
Hierarchy
ledtek.com is the parent zone for mail.ledtek.com.
IP Addresses
ledtek.com points to a single IP number: 45.33.82.87.
Additional host names — klrs.ca, nfhomeimprovement.com, roaming-initiative.com and two others — share IP numbers with ledtek.com.
Name Servers
ledtek.com is delegated to two name servers: kevin.quicns.net and jon.quicns.org.
ledtek.com shares its name server setup with other domains, including pecaimexpltd.com, ottuhr.com, e-kapetanios.gr and two others.
ledtek.com partially shares its NS delegation with several other domains, including bvbc.co.uk, wilcks.dk, guinchotaubate.com.br and two others.
In DNS configurations, these name servers often share authority with kevin.quicns.cloud, mike.quicns.cloud, jon.quicns.com and 5 other name servers.
kevin.quicns.net resolves to 64.66.241.1. jon.quicns.org resolves to 64.66.240.1. Both host names point to a single IP number.