codepak.com - dns.ninja
codepak.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | sl1.sedo.com ⚠️ Not in zone NS records | ||||||
| A | 91.195.240.173🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| NS | sl2.sedo.com ⚠️ Not in zone NS records | ||||||
| A | 91.195.241.173🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
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=1782996551 | ||||||
Same first word
Similar names
decopak.nl |
decopak.com |
podcake.com |
apkcode.com |
doepack.com |
adpocke.com |
kapcode.com |
cakepod.com |
peakdco.com |
cokepda.com |
codpeak.com |
docapek.at |
edopack.com |
codekap.com |
DNS History
18 records (2 active, 16 former)
○NSns-ca.1and1-dns.biz2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○NSns-ca.1and1-dns.ca2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○NSns-ca.1and1-dns.com2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○NSns-ca.1and1-dns.org2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○NSns1.sedoparking.com2015-07-16 → 2019-12-29 · 7 obs
● 2015-07-16 18:17:54
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2017-01-31 00:07:36
● 2019-12-29 18:39:20
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2017-01-31 00:07:36
● 2019-12-29 18:39:20
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
○NSns2.sedoparking.com2015-07-16 → 2019-12-29 · 7 obs
● 2015-07-16 18:17:54
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2017-01-31 00:07:36
● 2019-12-29 18:39:20
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2017-01-31 00:07:36
● 2019-12-29 18:39:20
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
●NSsl1.sedo.com2026-05-04 → 2026-07-02 · 3 obs
○ 2019-12-29 18:39:20
● 2026-05-04 03:02:54
● 2026-07-02 12:59:50
● 2026-05-04 03:02:54
● 2026-07-02 12:59:50
●NSsl2.sedo.com2026-05-04 → 2026-07-02 · 3 obs
○ 2019-12-29 18:39:20
● 2026-05-04 03:02:54
● 2026-07-02 12:59:50
● 2026-05-04 03:02:54
● 2026-07-02 12:59:50
○MXlocalhost2019-12-29 → 2026-05-22 · 5 obs
○ 2017-01-31 00:07:36
● 2019-12-29 18:39:20
● 2026-05-22 09:12:20
○ 2026-06-23 15:29:22
○ 2026-07-02 12:59:50
● 2019-12-29 18:39:20
● 2026-05-22 09:12:20
○ 2026-06-23 15:29:22
○ 2026-07-02 12:59:50
○MXmail.nickstel.com2015-07-16 → 2016-02-11 · 4 obs
● 2015-07-16 18:17:54
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2026-07-02 12:59:50
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2026-07-02 12:59:50
○MXmx00.1and1.com2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○MXmx01.1and1.com2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○A2607:f1c0:100f:f000::2db2017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○A64.190.63.2222026-05-04 → 2026-07-02 · 2 obs
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
○ 2026-07-02 12:59:50
○A72.52.4.912015-07-16 → 2016-02-11 · 4 obs
● 2015-07-16 18:17:54
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2026-07-02 12:59:50
● 2016-02-11 08:06:28
○ 2016-06-17 20:07:48
○ 2026-07-02 12:59:50
○A74.208.236.2442017-01-31 → 2017-01-31 · 4 obs
○ 2016-06-17 20:07:48
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
● 2017-01-31 00:07:36
○ 2019-12-29 18:39:20
○ 2026-07-02 12:59:50
○A91.195.240.1262019-12-29 → 2019-12-29 · 4 obs
○ 2017-01-31 00:07:36
● 2019-12-29 18:39:20
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
● 2019-12-29 18:39:20
○ 2026-05-04 03:02:54
○ 2026-07-02 12:59:50
○A91.195.241.2322026-05-04 → 2026-05-22 · 5 obs
○ 2019-12-29 18:39:20
● 2026-05-04 03:02:54
● 2026-05-22 09:12:20
○ 2026-06-23 15:29:22
○ 2026-07-02 12:59:50
● 2026-05-04 03:02:54
● 2026-05-22 09:12:20
○ 2026-06-23 15:29:22
○ 2026-07-02 12:59:50
🔍 DNS Trace
Analysis
Name Servers
codepak.com uses two name servers for its delegation: sl1.sedo.com and sl2.sedo.com.
codepak.com uses the same name servers as several other domains — among them starjam.de, mansus.de, winbo.eu and two more.
At least some of codepak.com's name servers are shared with other domains, for example n61.co.uk and sso.eisline.de.
Each of sl1.sedo.com and sl2.sedo.com has one IP address: sl1.sedo.com uses 91.195.240.173 and sl2.sedo.com uses 91.195.241.173.