fimo.in - dns.ninja
fimo.in
| 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 | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1783674658 | ||||||
Same first word
Similar names
DNS History
18 records (2 active, 16 former)
○NSns1.bodis.com2016-12-14 → 2016-12-30 · 5 obs
○ 2016-09-26 11:26:54
● 2016-12-14 03:32:14
● 2016-12-30 10:50:20
○ 2017-12-12 20:31:30
○ 2026-07-10 09:28:46
● 2016-12-14 03:32:14
● 2016-12-30 10:50:20
○ 2017-12-12 20:31:30
○ 2026-07-10 09:28:46
○NSns1.parkingcrew.net2016-03-06 → 2016-09-26 · 4 obs
● 2016-03-06 10:29:48
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
○NSns1.sedoparking.com2017-12-12 → 2017-12-12 · 4 obs
○ 2016-12-30 10:50:20
● 2017-12-12 20:31:30
○ 2026-04-04 09:41:38
○ 2026-07-10 09:28:46
● 2017-12-12 20:31:30
○ 2026-04-04 09:41:38
○ 2026-07-10 09:28:46
○NSns2.bodis.com2016-12-14 → 2016-12-30 · 5 obs
○ 2016-09-26 11:26:54
● 2016-12-14 03:32:14
● 2016-12-30 10:50:20
○ 2017-12-12 20:31:30
○ 2026-07-10 09:28:46
● 2016-12-14 03:32:14
● 2016-12-30 10:50:20
○ 2017-12-12 20:31:30
○ 2026-07-10 09:28:46
○NSns2.parkingcrew.net2016-03-06 → 2016-09-26 · 4 obs
● 2016-03-06 10:29:48
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
○NSns2.sedoparking.com2017-12-12 → 2017-12-12 · 4 obs
○ 2016-12-30 10:50:20
● 2017-12-12 20:31:30
○ 2026-04-04 09:41:38
○ 2026-07-10 09:28:46
● 2017-12-12 20:31:30
○ 2026-04-04 09:41:38
○ 2026-07-10 09:28:46
●NSsl1.sedo.com2026-04-04 → 2026-07-10 · 3 obs
○ 2017-12-12 20:31:30
● 2026-04-04 09:41:38
● 2026-07-10 09:28:46
● 2026-04-04 09:41:38
● 2026-07-10 09:28:46
●NSsl2.sedo.com2026-04-04 → 2026-07-10 · 3 obs
○ 2017-12-12 20:31:30
● 2026-04-04 09:41:38
● 2026-07-10 09:28:46
● 2026-04-04 09:41:38
● 2026-07-10 09:28:46
○MXexchange.dewile.net2016-07-17 → 2016-07-17 · 4 obs
○ 2016-03-14 10:22:36
● 2016-07-17 15:15:16
○ 2016-09-26 11:26:54
○ 2026-07-10 09:28:46
● 2016-07-17 15:15:16
○ 2016-09-26 11:26:54
○ 2026-07-10 09:28:46
○MXlocalhost2017-12-12 → 2026-04-25 · 4 obs
○ 2016-12-14 03:32:14
● 2017-12-12 20:31:30
● 2026-04-25 11:45:02
○ 2026-07-10 09:28:46
● 2017-12-12 20:31:30
● 2026-04-25 11:45:02
○ 2026-07-10 09:28:46
○MXmail.h-email.net2016-03-06 → 2016-09-26 · 6 obs
● 2016-03-06 10:29:48
● 2016-03-14 10:22:36
○ 2016-07-17 15:15:16
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
● 2016-03-14 10:22:36
○ 2016-07-17 15:15:16
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
○A185.53.177.92016-09-26 → 2016-09-26 · 4 obs
○ 2016-07-17 15:15:16
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
● 2016-09-26 11:26:54
○ 2016-12-14 03:32:14
○ 2026-07-10 09:28:46
○A185.53.179.222016-07-17 → 2016-07-17 · 4 obs
○ 2016-03-14 10:22:36
● 2016-07-17 15:15:16
○ 2016-09-26 11:26:54
○ 2026-07-10 09:28:46
● 2016-07-17 15:15:16
○ 2016-09-26 11:26:54
○ 2026-07-10 09:28:46
○A199.59.242.1502016-12-30 → 2016-12-30 · 4 obs
○ 2016-12-14 03:32:14
● 2016-12-30 10:50:20
○ 2017-12-12 20:31:30
○ 2026-07-10 09:28:46
● 2016-12-30 10:50:20
○ 2017-12-12 20:31:30
○ 2026-07-10 09:28:46
○A199.59.243.1202016-12-14 → 2016-12-14 · 4 obs
○ 2016-09-26 11:26:54
● 2016-12-14 03:32:14
○ 2016-12-30 10:50:20
○ 2026-07-10 09:28:46
● 2016-12-14 03:32:14
○ 2016-12-30 10:50:20
○ 2026-07-10 09:28:46
○A54.72.9.512016-03-06 → 2016-03-14 · 4 obs
● 2016-03-06 10:29:48
● 2016-03-14 10:22:36
○ 2016-07-17 15:15:16
○ 2026-07-10 09:28:46
● 2016-03-14 10:22:36
○ 2016-07-17 15:15:16
○ 2026-07-10 09:28:46
○A72.52.4.1202017-12-12 → 2017-12-12 · 4 obs
○ 2016-12-30 10:50:20
● 2017-12-12 20:31:30
○ 2026-04-04 09:41:38
○ 2026-07-10 09:28:46
● 2017-12-12 20:31:30
○ 2026-04-04 09:41:38
○ 2026-07-10 09:28:46
○A91.195.241.2322026-04-04 → 2026-04-25 · 4 obs
○ 2017-12-12 20:31:30
● 2026-04-04 09:41:38
● 2026-04-25 11:45:02
○ 2026-07-10 09:28:46
● 2026-04-04 09:41:38
● 2026-04-25 11:45:02
○ 2026-07-10 09:28:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns1.registry.in, ns2.registry.in, ns3.registry.in, ns4.registry.in | - |
| fimo.in | sl2.sedo.com, sl1.sedo.com | - |
✅ Authoritative Response
Server:91.195.240.173
NS records: sl2.sedo.com, sl1.sedo.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fimo.in (unsigned zone)
⏱️ Timing
Total: 2565ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.241.232 |
| NS | 2 | sl1.sedo.com, sl2.sedo.com |
| MX | 1 | localhost (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | sl1.sedo.com hostmaster.sedo.de |
Analysis
Name Servers
fimo.in is served by two delegated name servers, sl1.sedo.com and sl2.sedo.com.
fimo.in uses the same name servers as several other domains — among them mail.codc.de, nicegirls.eu, gameads.de and two more.
sl1.sedo.com → 91.195.240.173 and sl2.sedo.com → 91.195.241.173: one IP number per host name.