`bf-component.ru`

DNSSEC	⚠️ Not signed
A	87.236.16.35^{🇷🇺 BEGET-AS87.236.16.0/24 BEGET.RU}
		PTR	`ssl.liberty.beget.com`
NS	`ns1.beget.com` ⭐
		A	5.101.159.11^{🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU}
			PTR	`ns1.beget.com`
NS	`ns1.beget.pro`
		A	5.101.159.11^{🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU}
			PTR	`ns1.beget.com`
NS	`ns1.beget.ru` ⚠️ Not in parent delegation
		A	5.101.159.11^{🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU}
			PTR	`ns1.beget.com`
NS	`ns2.beget.com`
		A	185.50.27.12^{🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU}
			PTR	`ns2.beget.com`
NS	`ns2.beget.pro`
		A	185.50.27.12^{🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU}
			PTR	`ns2.beget.com`
NS	`ns2.beget.ru` ⚠️ Not in parent delegation
		A	185.50.27.12^{🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU}
			PTR	`ns2.beget.com`
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 include:_spf.yandex.ru include:beget.com ~all`
SOA	`ns1.beget.com`hostmaster@beget.com serial=1729179980

`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.net`hostmaster@ripn.net serial=4068289

Same first word

bf-component.ru

DNS History

15 records (8 active, 7 former)

○NSns.mtw.ru2008-11-24 → 2019-01-03 · 4 obs

● 2008-11-24 16:32:02
● 2019-01-03 17:22:08
○ 2020-03-18 10:08:06
○ 2026-03-27 03:21:42

●NSns1.beget.com2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

●NSns1.beget.pro2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

●NSns1.beget.ru2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

○NSns1.mtw.ru2008-11-24 → 2019-01-03 · 4 obs

● 2008-11-24 16:32:02
● 2019-01-03 17:22:08
○ 2020-03-18 10:08:06
○ 2026-03-27 03:21:42

●NSns2.beget.com2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

●NSns2.beget.pro2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

●NSns2.beget.ru2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

●MXmx.yandex.net2020-03-18 → 2026-03-27 · 3 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
● 2026-03-27 03:21:42

○MXpochta.mtw.ru2008-11-24 → 2019-01-03 · 4 obs

● 2008-11-24 16:32:02
● 2019-01-03 17:22:08
○ 2020-03-18 10:08:06
○ 2026-03-27 03:21:42

○A194.135.105.2032008-11-24 → 2008-11-24 · 3 obs

● 2008-11-24 16:32:02
○ 2015-08-13 23:24:18
○ 2026-03-27 03:21:42

○A37.228.90.122018-03-05 → 2019-01-03 · 5 obs

○ 2017-05-23 23:35:30
● 2018-03-05 16:36:22
● 2019-01-03 17:22:08
○ 2020-03-18 10:08:06
○ 2026-03-27 03:21:42

●A87.236.16.352026-02-27 → 2026-03-27 · 3 obs

○ 2020-03-18 10:08:06
● 2026-02-27 21:49:48
● 2026-03-27 03:21:42

○A87.236.16.642020-03-18 → 2020-03-18 · 4 obs

○ 2019-01-03 17:22:08
● 2020-03-18 10:08:06
○ 2026-02-27 21:49:48
○ 2026-03-27 03:21:42

○A93.95.98.872015-08-13 → 2017-05-23 · 5 obs

○ 2008-11-24 16:32:02
● 2015-08-13 23:24:18
● 2017-05-23 23:35:30
○ 2018-03-05 16:36:22
○ 2026-03-27 03:21:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, d.dns.ripn.net, f.dns.ripn.net, b.dns.ripn.net...	-
bf-component.ru	ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro	-

✅ Authoritative Response

Server:5.101.159.11

NS records: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bf-component.ru (unsigned zone)

⏱️ Timing

Total: 1378ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`87.236.16.35`
NS	6	`ns2.beget.ru, ns1.beget.ru...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 include:_spf.yandex.ru include:be`
SOA	1	`ns1.beget.com hostmaster.beget.com`

Analysis

IP Addresses

bf-component.ru points to a single IP number: 87.236.16.35.

Other host names, for instance konopel.ru, megazdrav.ru, 1smm.info, kino-film.su and www.velesart.ru share IP numbers with bf-component.ru.

Name Servers

bf-component.ru is delegated to six name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro, ns2.beget.pro, ns1.beget.ru and ns2.beget.ru.

bf-component.ru at least partially shares name servers with other domains, for instance facemeet.fun, ramkioptom.ru, hotel87.ru, sauna142.ru and product-managers.store.

Two IPs used: 5.101.159.11 and 185.50.27.12.

ns1.beget.com points to 5.101.159.11.

ns2.beget.com points to 185.50.27.12.

ns1.beget.pro points to 5.101.159.11.

ns2.beget.pro points to 185.50.27.12.

ns1.beget.ru points to 5.101.159.11.

ns2.beget.ru points to 185.50.27.12.

Hosts pointing to 5.101.159.11: ns1.beget.com, ns1.beget.pro and ns1.beget.ru.

Hosts pointing to 185.50.27.12: ns2.beget.com, ns2.beget.pro and ns2.beget.ru.

Mail Servers

bf-component.ru is handled by a single mail server, mx.yandex.net.

bf-component.ru uses the same mail server configuration as other domains, such as dalico.ru, komavto.ru, agat-zavod.ru, sakmar.com.tr and ornekmakina.com.tr.

bf-component.ru shares at least some mail servers with other domains, for instance steelline54.ru, emikhno.com, zakari.ru and progaonline.com.

mx.yandex.net resolves to two IP numbers: 2a02:6b8::311 and 77.88.21.249.

bf-component.ru - robtex.com

bf-component.ru

ru

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`bf-component.ru`

`ru`