agfc.ru - robtex.com
agfc.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 37.140.192.16🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru | ||||||
| PTR | server38.hosting.reg.ru | ||||||
| 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=7 | ||||||
ru
| DNSSEC | ⚠️ Not signed | ||||||
| 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=4067830 | ||||||
Same first word
agfc.blogspot.de |
agfc.ch |
agfc.com.au |
agfc.de |
agfc.org |
agfc.blogspot.fr |
agfc.in |
agfc.net |
agfc.com |
agfc.org.au |
agfc.ru |
agfc.com.ar |
agfc.co.uk |
agfc.qc.ca |
Similar names
DNS History
12 records (4 active, 8 former)
●NSdns1.yandex.net2026-02-17 → 2026-03-14 · 3 obs
● 2026-02-17 01:23:52
● 2026-03-14 06:37:48
●NSdns2.yandex.net2026-02-17 → 2026-03-14 · 3 obs
● 2026-02-17 01:23:52
● 2026-03-14 06:37:48
○NSns1.poishi.com2015-07-09 → 2017-01-15 · 16 obs
● 2015-09-14 15:55:06
○ 2015-12-28 08:41:32
○ 2016-02-03 18:53:02
● 2016-02-05 20:14:42
● 2016-02-08 03:38:28
○ 2016-03-13 07:01:40
● 2016-06-05 15:30:56
● 2016-06-23 12:01:04
○ 2016-09-12 22:35:30
● 2016-10-03 15:22:08
○ 2016-11-23 06:24:50
● 2016-12-07 10:49:10
● 2017-01-15 15:53:48
○ 2026-02-17 01:23:52
○ 2026-03-14 06:37:48
○NSns1.sedoparking.com2015-07-09 → 2017-01-15 · 16 obs
○ 2015-09-14 15:55:06
● 2015-12-28 08:41:32
● 2016-02-03 18:53:02
○ 2016-02-05 20:14:42
○ 2016-02-08 03:38:28
● 2016-03-13 07:01:40
○ 2016-06-05 15:30:56
○ 2016-06-23 12:01:04
● 2016-09-12 22:35:30
○ 2016-10-03 15:22:08
● 2016-11-23 06:24:50
○ 2016-12-07 10:49:10
● 2017-01-15 15:53:48
○ 2026-02-17 01:23:52
○ 2026-03-14 06:37:48
○NSns2.poishi.com2015-09-14 → 2016-10-03 · 8 obs
● 2015-09-14 15:55:06
○ 2015-12-28 08:41:32
○ 2016-03-13 07:01:40
● 2016-06-05 15:30:56
● 2016-10-03 15:22:08
○ 2016-11-23 06:24:50
○ 2026-03-14 06:37:48
○NSns2.sedoparking.com2015-07-09 → 2017-01-15 · 10 obs
○ 2015-09-14 15:55:06
● 2015-12-28 08:41:32
● 2016-03-13 07:01:40
○ 2016-06-05 15:30:56
○ 2016-10-03 15:22:08
● 2016-11-23 06:24:50
● 2017-01-15 15:53:48
○ 2026-02-17 01:23:52
○ 2026-03-14 06:37:48
○MXlocalhost2016-12-07 → 2017-01-15 · 5 obs
● 2016-12-07 10:49:10
● 2017-01-15 15:53:48
○ 2026-02-17 01:23:52
○ 2026-03-14 06:37:48
○MXmail.nickstel.com2015-07-09 → 2016-03-13 · 7 obs
● 2016-02-03 18:53:02
○ 2016-02-05 20:14:42
● 2016-02-08 03:38:28
● 2016-03-13 07:01:40
○ 2016-06-05 15:30:56
○ 2026-03-14 06:37:48
●MXmx.yandex.net2026-02-17 → 2026-03-14 · 3 obs
● 2026-02-17 01:23:52
● 2026-03-14 06:37:48
●A37.140.192.162026-02-17 → 2026-03-14 · 3 obs
● 2026-02-17 01:23:52
● 2026-03-14 06:37:48
○A72.52.4.912015-07-09 → 2016-12-07 · 10 obs
○ 2015-09-14 15:55:06
● 2015-12-28 08:41:32
● 2016-03-13 07:01:40
○ 2016-06-05 15:30:56
○ 2016-09-12 22:35:30
● 2016-10-03 15:22:08
● 2016-12-07 10:49:10
○ 2017-01-15 15:53:48
○ 2026-03-14 06:37:48
○A82.98.86.1672015-07-09 → 2017-01-15 · 11 obs
● 2015-09-14 15:55:06
○ 2015-12-28 08:41:32
○ 2016-03-13 07:01:40
● 2016-06-05 15:30:56
● 2016-09-12 22:35:30
○ 2016-10-03 15:22:08
○ 2016-12-07 10:49:10
● 2017-01-15 15:53:48
○ 2026-02-17 01:23:52
○ 2026-03-14 06:37:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | f.dns.ripn.net, b.dns.ripn.net, e.dns.ripn.net, d.dns.ripn.net... | - |
| agfc.ru | 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 agfc.ru (unsigned zone)
⏱️ Timing
Total: 1308ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 37.140.192.16 |
| 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
IP Addresses
agfc.ru points to a single IP number: 37.140.192.16.
other host names for instance rcs.ru, peskostrui.com, rcsi.ru, server38.hosting.reg.ru and mail.transazur.com share IP numbers with agfc.ru.
Name Servers
agfc.ru is delegated to two name servers: dns1.yandex.net and dns2.yandex.net.
agfc.ru shares the same name server setup as other domains, for example mercury-art.ru, wc3.ru, nip.perm.ru, savasin.net and simatix.ru.
agfc.ru at least partially shares name servers with other domains, for instance is-media.ru, pecrus.com, stt-nn.ru, x-sun.ru and slcode.ru.
These name servers are often 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
agfc.ru is handled by a single mail server, mx.yandex.net.
agfc.ru shares the same mail server setup as other domains, for instance ipmem.com, nature-health.ru, all4bath.ru, svao-clinic.ru and kupiploshadku.ru.
agfc.ru shares at least partially some mail servers with other domains, for instance markapalet.com, td-1.com and propozitsiya.com.
Host mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.