github73.space - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`github73.space`

DNSSEC	⚠️ Not signed
A	91.107.126.24
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}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU194.58.117.0/24}
			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}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU194.58.117.0/24}
			PTR	`ns2.reg.ru`
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.reg.ru`hostmaster@ns1.reg.ru serial=1766516993

`space`

	DNSSEC	⚠️ Not signed
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1789931025

⚠️ On DNS blocklist: spam-tlds

Same first word

github73.space

Similar names

github37.now.sh

DNS History

4 records (4 active, 0 former)

●NSns1.reg.ru2026-09-08 → 2026-09-20 · 2 obs

● 2026-09-08 16:16:32
● 2026-09-20 19:32:10

●NSns2.reg.ru2026-09-08 → 2026-09-20 · 2 obs

● 2026-09-08 16:16:32
● 2026-09-20 19:32:10

●MXmx.yandex.net2026-09-08 → 2026-09-20 · 2 obs

● 2026-09-08 16:16:32
● 2026-09-20 19:32:10

●A91.107.126.242026-09-08 → 2026-09-20 · 2 obs

● 2026-09-08 16:16:32
● 2026-09-20 19:32:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
space	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
github73.space	ns1.reg.ru, ns2.reg.ru	-

✅ Authoritative Response

Server:176.99.13.12

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for github73.space (unsigned zone)

⏱️ Timing

Total: 2132ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)

Analysis

IP Addresses

github73.space directs to one IP number, which is 91.107.126.24.

Name Servers

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

Host names resolving to 10 IP numbers:

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

github73.space routes its mail through a single mail server, mx.yandex.net.

mx.yandex.net has two IP addresses: 77.88.21.249 and 2a02:6b8::311.