transfiles.ru - robtex.com
transfiles.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 65.108.228.44🇫🇮 Hetzner65.108.0.0/16 HETZNER-DC | ||||||
| PTR | static.44.228.108.65.clients.your-server.de | ||||||
| NS | ns1.transfiles.ru ⭐ | ||||||
| A | 65.108.228.44🇫🇮 Hetzner65.108.0.0/16 HETZNER-DC | ||||||
| PTR | static.44.228.108.65.clients.your-server.de | ||||||
| NS | ns2.transfiles.ru | ||||||
| A | 5.78.42.222🇺🇸 HETZNER-CLOUD3-AS5.78.42.0/24 | ||||||
| PTR | static.222.42.78.5.clients.your-server.de | ||||||
| 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 | ns1.transfiles.ruadmin@transfiles.ru 2026-01-04 #1 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4068484 | ||||||
rank #6157 in the tld
WOT: SAFE (72/100)
📈 Tranco rank: #43,579
Previously MX for
transfiles.ru |
Subdomains
Same first word
transfiles.com |
transfiles.ru |
Similar names
DNS History
9 records (4 active, 5 former)
○NSdns1.yandex.net2016-01-21 → 2020-11-26 · 4 obs
● 2020-11-26 17:01:02
○ 2026-02-27 14:34:40
○ 2026-04-12 06:06:08
○NSdns2.yandex.net2016-01-21 → 2020-11-26 · 4 obs
● 2020-11-26 17:01:02
○ 2026-02-27 14:34:40
○ 2026-04-12 06:06:08
●NSns1.transfiles.ru2026-02-27 → 2026-04-12 · 3 obs
● 2026-02-27 14:34:40
● 2026-04-12 06:06:08
●NSns2.transfiles.ru2026-02-27 → 2026-04-12 · 3 obs
● 2026-02-27 14:34:40
● 2026-04-12 06:06:08
●MXmx.yandex.net2016-04-13 → 2026-04-12 · 3 obs
● 2016-04-13 12:41:02
● 2026-04-12 06:06:08
○MXtransfiles.ru2016-01-21 → 2016-01-21 · 3 obs
○ 2016-04-13 12:41:02
○ 2026-04-12 06:06:08
○A194.28.219.42016-01-21 → 2020-11-26 · 7 obs
● 2016-11-19 18:50:06
○ 2017-07-02 05:15:12
● 2017-11-15 07:59:34
● 2020-11-26 17:01:02
○ 2026-02-27 14:34:40
○ 2026-04-12 06:06:08
○A62.176.19.1922017-07-02 → 2020-11-26 · 7 obs
● 2017-07-02 05:15:12
○ 2017-11-15 07:59:34
○ 2018-10-12 14:56:20
● 2020-11-26 17:01:02
○ 2026-02-27 14:34:40
○ 2026-04-12 06:06:08
●A65.108.228.442026-02-27 → 2026-04-12 · 3 obs
● 2026-02-27 14:34:40
● 2026-04-12 06:06:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| transfiles.ru | ns2.transfiles.ru, ns1.transfiles.ru | 2 records |
✅ Authoritative Response
Server:5.78.42.222
NS records: ns2.transfiles.ru, ns1.transfiles.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for transfiles.ru (unsigned zone)
⏱️ Timing
Total: 682ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.108.228.44 |
| NS | 2 | ns1.transfiles.ru, ns2.transfiles.ru |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | ns1.transfiles.ru admin.transfiles.ru |
📌 Glue Records Collected
Total: 2
In-bailiwick: 2 (ns2.transfiles.ru, ns1.transfiles.ru)
Analysis
Hierarchy
transfiles.ru is a parent of ns1.transfiles.ru and ns2.transfiles.ru.
IP Addresses
transfiles.ru points to IP number 65.108.228.44.
Other host names, for example ns1.transfiles.ru and static.44.228.108.65.clients.your-server.de, share IPs with transfiles.ru.
Name Servers
transfiles.ru is delegated to two name servers: ns1.transfiles.ru and ns2.transfiles.ru.
transfiles.ru shares the same name server setup as other domains, for instance cputronic.com.
Host names with one IP number:
ns1.transfiles.ru points to: 65.108.228.44.
ns2.transfiles.ru points to: 5.78.42.222.
Mail Servers
transfiles.ru is handled by a single mail server, mx.yandex.net.
transfiles.ru shares the same mail server setup as other domains, for instance dezfog.ru, bsc-food.ru, khorog.ru, sqlcom.ru and iskra-bisert.ru.
transfiles.ru shares mail servers with other domains at least partially; for instance linkrr.app, msh.su, pavlova-kmv.ru, kuzniui.ru and meritec.su.
mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.