bugser.ru - dns.ninja

`bugser.ru`

DNSSEC	⚠️ Not signed
NS	`ns1.reg.ru` ⭐
		A	2a00:f940:9::1:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.11^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
NS	`ns2.reg.ru`
		A	2a00:f940:9::1:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.12^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
MX	`mx.yandex.ru` ⭐
		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.reg.ru`hostmaster@ns1.reg.ru serial=1760596234

`ru`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.dns.ripn.net` ⭐
	NS	`b.dns.ripn.net`
	NS	`c.tld-servers.ru`
	NS	`d.dns.ripn.net`
	NS	`e.dns.ripn.net`
	NS	`f.dns.ripn.net`
	SOA	`a.dns.ripn.net`hostmaster@ripn.net serial=4069915

Same first word

bugser.com

bugser.ru

Similar names

regbus.net

subreg.de

subreg.org

subreg.biz

grebus.com

grubse.com

rusebg.com

suberg.net

burges.be

bgruse.com

busreg.com

bruges.sakura.ne.jp

bruges.it

grubes.com

gubers.com

bsurge.com

burges.com.tw

bergus.com.br

gerbus.ca

bregus.com

bruges.com

subreg.pl

esburg.com

bugers.com

regbus.pl

bruges.org

seburg.com

bregus.com.ua

subreg.com

rebugs.com

grubes.at

bruegs.com

grubes.de

gubser.us

surbeg.com

gubser.de

gubser.com

bregus.ru

gubser.net

busreg.eu

burges.org

gubser.org

regsub.com

ubregs.com

gubres.com

bruges.de

usberg.net

bruges.info

subreg.net

bergus.s3.amazonaws.com

bregus.pl

busreg.co.za

bruges.co.jp

burges.at

bruges.site

subreg.cz

burges.info

suberg.eu

usberg.de

burges.it

suberg.cz

bergus.org

subreg.sk

suberg.ch

regbus.com

subreg.ru

bregus.eu

gubser.ch

bruges.altervista.org

bruges.ph

burges.eu

burges.de

bregus.de

bruges.be

DNS History

4 records (3 active, 1 former)

●NSns1.reg.ru2017-04-18 → 2026-08-08 · 2 obs

● 2017-04-18 21:33:16
● 2026-08-08 19:21:12

●NSns2.reg.ru2017-04-18 → 2026-08-08 · 2 obs

● 2017-04-18 21:33:16
● 2026-08-08 19:21:12

●MXmx.yandex.ru2026-03-02 → 2026-08-08 · 2 obs

● 2026-03-02 09:16:58
● 2026-08-08 19:21:12

○A31.31.204.1612017-04-18 → 2017-04-18 · 3 obs

● 2017-04-18 21:33:16
○ 2026-03-02 09:16:58
○ 2026-08-08 19:21:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, b.dns.ripn.net, c.tld-servers.ru, d.dns.ripn.net...	-
bugser.ru	ns1.reg.ru, ns2.reg.ru	20 records

✅ Authoritative Response

Server:176.99.13.11

NS records: ns1.reg.ru, ns2.reg.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bugser.ru (unsigned zone)

⏱️ Timing

Total: 678ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.reg.ru, ns2.reg.ru`
MX	1	`mx.yandex.ru (pri: 0)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

📌 Glue Records Collected

Total: 20

Out-of-bailiwick: 20 (ns1.reg.ru, ns1.reg.ru, ns1.reg.ru...)

Analysis

Name Servers

bugser.ru has two authoritative name servers — ns1.reg.ru and ns2.reg.ru.

bugser.ru uses the same name servers as several other domains — among them phys.su, cok-niime.ru, rubycom.ru and two more.

The name servers for bugser.ru overlap at least partially with those of other domains — for example perevod-kazan.ru.

These name servers commonly appear in combination with the name servers ns1.logol.ru.

Hostnames that resolve to 10 IP addresses:

ns1.reg.ru points to 176.99.13.11, 176.99.13.13, 176.99.13.15 and 7 other IP addresses.

ns2.reg.ru points to 176.99.13.12, 176.99.13.14, 176.99.13.16 and 7 other IP addresses.

Mail Servers

Mail for bugser.ru is handled by a single mail server, mx.yandex.ru.

bugser.ru uses an identical mail server configuration to several other domains — among them mosfracht.ru, artleks.ru, s-smirnov.ru and two more.

bugser.ru has at least partial mail server overlap with other domains such as max-fm.ru, vectormm.net, teacher19.ru and two more.

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