ferdiyilmaz.com - robtex.com
ferdiyilmaz.com
| DNSSEC | ⚠️ Not signed | ||||||
| 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=6 | ||||||
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=1774516927 | ||||||
Subdomains
mail.ferdiyilmaz.com |
Same first word
ferdiyilmaz.com |
DNS History
6 records (3 active, 3 former)
●NSdns1.yandex.net2017-03-16 → 2026-03-26 · 3 obs
● 2017-03-16 11:16:00
● 2026-03-26 09:24:00
●NSdns2.yandex.net2017-03-16 → 2026-03-26 · 3 obs
● 2017-03-16 11:16:00
● 2026-03-26 09:24:00
○NSns1.isimtescil.net2015-08-04 → 2016-07-15 · 4 obs
● 2016-07-15 02:12:34
○ 2017-03-16 11:16:00
○ 2026-03-26 09:24:00
○MX1499129302.pamx1.hotmail.com2015-08-04 → 2016-07-15 · 4 obs
● 2016-07-15 02:12:34
○ 2017-03-16 11:16:00
○ 2026-03-26 09:24:00
●MXmx.yandex.net2017-03-16 → 2026-03-26 · 3 obs
● 2017-03-16 11:16:00
● 2026-03-26 09:24:00
○A81.22.98.662015-08-04 → 2016-07-15 · 4 obs
● 2016-07-15 02:12:34
○ 2017-03-16 11:16:00
○ 2026-03-26 09:24:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ferdiyilmaz.com | 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 ferdiyilmaz.com (unsigned zone)
⏱️ Timing
Total: 1378ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns2.yandex.net, dns1.yandex.net |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | dns1.yandex.net dns-hosting.yandex.ru |
Analysis
Hierarchy
The parent of mail.ferdiyilmaz.com is ferdiyilmaz.com.
Name Servers
Two name servers dns1.yandex.net and dns2.yandex.net handle the delegation for ferdiyilmaz.com.
ferdiyilmaz.com shares the same name server setup as other domains, for instance pokleykaoboev.pro, bcsn.ru, sportpole.ru, okinava35.ru and progela.com.tr.
ferdiyilmaz.com at least partially shares name servers with other domains, for instance tehnokratia.ru, gruzovoz.org, cska-tv.ru, pozaronline.net and platus.com.tr.
These name servers are commonly used with dns1.yandex.ru and dns2.yandex.ru.
Host names with two IP numbers:
dns1.yandex.net points to 2a02:6b8::213 and 213.180.204.213.
dns2.yandex.net points to 2a02:6b8:0:1::213 and 93.158.134.213.
Mail Servers
ferdiyilmaz.com is handled by a single mail server, mx.yandex.net.
ferdiyilmaz.com uses the same mail server setup as other domains, for instance leventelektrik.biz, goodsurfing.org, elifozdogan.com, zoldi.pro and merkury-vd.ru.
ferdiyilmaz.com shares some mail servers with other domains, for example breslavsky.ru, tomas.kz and art-lan.ru.
mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.