idiary.tk - robtex.com
idiary.tk
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns01.freenom.com ⭐ | ||||||
| A | 54.171.131.39🇮🇪 Amazon54.171.0.0/16 EC2 DUB prefix | ||||||
| PTR | ec2-54-171-131-39.eu-west-1.compute.amazonaws.com | ||||||
| NS | ns02.freenom.com | ||||||
| A | 52.19.156.76🇮🇪 Amazon52.18.0.0/15 EC2 DUB prefix | ||||||
| PTR | ec2-52-19-156-76.eu-west-1.compute.amazonaws.com | ||||||
| NS | ns03.freenom.com | ||||||
| A | 104.155.27.112🇧🇪 Google104.155.16.0/20 | ||||||
| PTR | 112.27.155.104.bc.googleusercontent.com | ||||||
| NS | ns04.freenom.com | ||||||
| A | 104.155.29.241🇧🇪 Google104.155.16.0/20 | ||||||
| PTR | 241.29.155.104.bc.googleusercontent.com | ||||||
| SOA | ns01.freenom.comsoa@freenom.com serial=1707912452 | ||||||
tk
| DNSSEC | ⚠️ Not signed | ||||||
| A | 217.119.57.22 | ||||||
| NS | a.ns.tk ⭐ | ||||||
| NS | b.ns.tk | ||||||
| NS | c.ns.tk | ||||||
| NS | d.ns.tk | ||||||
| SOA | a.ns.tkjoost\@zuurbier.dot.tk serial=1778152078 | ||||||
Same first word
Similar names
DNS History
15 records (4 active, 11 former)
●NSns01.freenom.com2020-01-20 → 2026-05-07 · 3 obs
○ 2017-03-30 05:53:04
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
●NSns02.freenom.com2020-01-20 → 2026-05-07 · 3 obs
○ 2017-03-30 05:53:04
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
●NSns03.freenom.com2020-01-20 → 2026-05-07 · 3 obs
○ 2017-03-30 05:53:04
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
●NSns04.freenom.com2020-01-20 → 2026-05-07 · 3 obs
○ 2017-03-30 05:53:04
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
● 2020-01-20 11:57:48
● 2026-05-07 18:51:16
○NSns1.hostinger.co.uk2015-08-14 → 2017-03-30 · 4 obs
● 2015-08-14 13:02:34
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○NSns2.hostinger.co.uk2015-08-14 → 2017-03-30 · 4 obs
● 2015-08-14 13:02:34
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○NSns3.hostinger.co.uk2015-08-14 → 2017-03-30 · 4 obs
● 2015-08-14 13:02:34
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○NSns4.hostinger.co.uk2015-08-14 → 2017-03-30 · 4 obs
● 2015-08-14 13:02:34
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○MXalt1.aspmx.l.google.com2016-03-10 → 2017-03-30 · 5 obs
○ 2015-12-05 13:47:40
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○MXalt2.aspmx.l.google.com2016-03-10 → 2017-03-30 · 5 obs
○ 2015-12-05 13:47:40
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○MXalt3.aspmx.l.google.com2016-03-10 → 2017-03-30 · 5 obs
○ 2015-12-05 13:47:40
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○MXalt4.aspmx.l.google.com2016-03-10 → 2017-03-30 · 5 obs
○ 2015-12-05 13:47:40
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○MXaspmx.l.google.com2016-03-10 → 2017-03-30 · 5 obs
○ 2015-12-05 13:47:40
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2016-03-10 03:28:38
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
○MXmx1.hostinger.co.uk2015-08-14 → 2015-12-05 · 4 obs
● 2015-08-14 13:02:34
● 2015-12-05 13:47:40
○ 2016-03-10 03:28:38
○ 2026-05-07 18:51:16
● 2015-12-05 13:47:40
○ 2016-03-10 03:28:38
○ 2026-05-07 18:51:16
○A31.220.16.1272015-08-14 → 2017-03-30 · 4 obs
● 2015-08-14 13:02:34
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
● 2017-03-30 05:53:04
○ 2020-01-20 11:57:48
○ 2026-05-07 18:51:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| tk | a.ns.tk, b.ns.tk, c.ns.tk, d.ns.tk | 8 records |
| idiary.tk | ns01.freenom.com, ns02.freenom.com, ns03.freenom.com, ns04.freenom.com | - |
✅ Authoritative Response
Server:104.155.27.112
NS records: ns01.freenom.com, ns02.freenom.com, ns03.freenom.com, ns04.freenom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tk (unsigned zone)
⏱️ Timing
Total: 644ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns01.freenom.com, ns02.freenom.com... |
| SOA | 1 | ns01.freenom.com soa.freenom.com |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (a.ns.tk, b.ns.tk, c.ns.tk...)
Analysis
Name Servers
idiary.tk is delegated to four name servers: ns01.freenom.com, ns02.freenom.com, ns03.freenom.com and ns04.freenom.com.
idiary.tk shares some name servers with other domains, for example kobe24mamba.gq, tubeproxy.tk, qvision.tk, phen.tk and chatnao.tk.
Host names with a single IP
ns01.freenom.com resolves to 54.171.131.39
ns02.freenom.com resolves to 52.19.156.76
ns03.freenom.com resolves to 104.155.27.112
ns04.freenom.com resolves to 104.155.29.241