fixpack.com.tr - dns.ninja
fixpack.com.tr
| DNSSEC | ⚠️ Not signed | ||||||
| A | 159.89.9.173🇩🇪 DIGITALOCEAN159.89.0.0/20 DigitalOcean | ||||||
| NS | dns1.yandex.net ⭐ | ||||||
| A | 2a02:6b8::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | dns1.yandex.net | ||||||
| A | 213.180.204.213🇷🇺 TELETECH213.180.192.0/19 Yandex network | ||||||
| PTR | dns1.yandex.net | ||||||
| NS | dns2.yandex.net | ||||||
| A | 2a02:6b8:0:1::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | dns2.yandex.net | ||||||
| A | 93.158.134.213🇷🇺 TELETECH93.158.128.0/18 Yandex enterprise network | ||||||
| PTR | dns2.yandex.net | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | v=spf1 redirect=_spf.yandex.net | ||||||
| SOA | dns1.yandex.netdns-hosting@yandex.ru serial=42 | ||||||
com.tr
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns73.ns.tr ⭐ ⚠️ Not in parent delegation | ||||||
| NS | ns43.ns.tr ⚠️ Not in parent delegation | ||||||
| NS | ns44.ns.tr ⚠️ Not in parent delegation | ||||||
| NS | ns61.ns.tr ⚠️ Not in parent delegation | ||||||
| NS | ns71.ns.tr ⚠️ Not in parent delegation | ||||||
| NS | ns72.ns.tr ⚠️ Not in parent delegation | ||||||
| NS | ns74.ns.tr ⚠️ Not in parent delegation | ||||||
| NS | ns75.ns.tr ⚠️ Not in parent delegation | ||||||
| SOA | ns73.ns.trhostmaster@trabis.gov.tr serial=1786245608 | ||||||
Same first word
Similar names
DNS History
5 records (4 active, 1 former)
●NSdns1.yandex.net2017-06-20 → 2026-08-09 · 2 obs
● 2026-08-09 05:08:58
●NSdns2.yandex.net2017-06-20 → 2026-08-09 · 2 obs
● 2026-08-09 05:08:58
●MXmx.yandex.net2017-06-20 → 2026-08-09 · 4 obs
○ 2026-07-09 21:18:44
● 2026-07-10 05:35:58
● 2026-08-09 05:08:58
●A159.89.9.1732026-03-17 → 2026-08-09 · 5 obs
● 2026-03-17 16:07:22
○ 2026-07-10 05:35:58
● 2026-08-09 05:08:56
● 2026-08-09 05:08:58
○A46.101.209.562017-06-20 → 2017-06-20 · 3 obs
○ 2026-03-17 16:07:22
○ 2026-08-09 05:08:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| tr | ns44.ns.tr, ns61.ns.tr, ns72.ns.tr, ns74.ns.tr... | 12 records |
| fixpack.com.tr | dns1.yandex.net, dns2.yandex.net | - |
✅ Authoritative Response
Server:213.180.204.213
NS records: dns1.yandex.net, dns2.yandex.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fixpack.com.tr (unsigned zone)
⏱️ Timing
Total: 1115ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 159.89.9.173 |
| MX | 1 | mx.yandex.net (pri: 10) |
| SOA | 1 | dns1.yandex.net dns-hosting.yandex.ru |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (ns44.ns.tr, ns44.ns.tr, ns61.ns.tr...)
Analysis
IP Addresses
fixpack.com.tr has exactly one IP address — 159.89.9.173.
Name Servers
The NS records for fixpack.com.tr delegate to dns1.yandex.net and dns2.yandex.net.
The name server configuration of fixpack.com.tr is shared with other domains, for instance null.moe, heytec.ru, muratsayin.com and two others.
fixpack.com.tr has at least partial name server overlap with other domains, such as snebol.ru, vayner.ru, k210.org and two others.
It is common to see these name servers used together with name servers dns1.yandex.ru and dns2.yandex.ru.
dns1.yandex.net resolves to 213.180.204.213 and 2a02:6b8::213. Likewise, dns2.yandex.net resolves to 93.158.134.213 and 2a02:6b8:0:1::213 — two IP addresses apiece.
Mail Servers
fixpack.com.tr uses one mail server — mx.yandex.net.
The mail server setup of fixpack.com.tr matches that of other domains such as keso.ru, shumov.net, boomaga.ru and two others.
At least some of the mail servers used by fixpack.com.tr are shared with other domains: plyxa.com, wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww.ru, ultaxi.com and two others among them.
mx.yandex.net has two IP addresses: 77.88.21.249 and 2a02:6b8::311.