`hyperpc.by`

DNSSEC	⚠️ Not signed
A	2a0a:7d80:1:7::109:3c1^{🇧🇾 BELPAK-AS2a0a:7d80:1::/48}
A	93.125.99.120^{🇧🇾 BELPAK-AS93.125.99.0/24 DELEGATED FROM BELPAK}
NS	`ns1.hoster.by` ⭐
		A	2a0a:7d80:1:1::6:0^{🇧🇾 BELPAK-AS2a0a:7d80:1::/48}
			PTR	`ns1.hoster.by`
		A	93.125.30.200^{🇧🇾 BELPAK-AS93.125.30.0/24 DELEGATED FROM BELPAK}
			PTR	`ns1.hoster.by`
NS	`ns2.hoster.by`
		A	2a0a:7d80:3:1::8^{🇧🇾 HOSTERBY-AS2a0a:7d80:3::/48 hoster.by Velcom-DC IPv6 route object}
			PTR	`net-2a0a-7d80-3-1-prefix-64.hosterby.com`
		A	185.179.82.104^{🇧🇾 BN-AS185.179.82.0/23 BN for HOSTERBY}
			PTR	`185-179-82-104.hosterby.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 +a +mx include:_spf.hoster.by ~all`
TXT	`yandex-verification: 34b7917794b19493`
TXT	`v=spf1 redirect=_spf.yandex.net`
SOA	`ns1.hoster.by`root@vh109.hoster.by 2022-03-03 #3

`by`

	DNSSEC	🔒 Signed (DS record present)
	NS	`dns1.tld.becloud.by` ⭐
	NS	`dns1.tld.becloudby.com`
	NS	`dns2.tld.becloudby.tech`
	NS	`dns3.tld.becloudby.tech`
	NS	`dns4.tld.becloudby.tech`
	NS	`dns7.tld.becloudby.com`
	SOA	`dns1.tld.becloud.by`support@becloud.by serial=2602170110

Same first word

hyperpc.co.jp

hyperpc.net

hyperpc.ru

hyperpc.ir

hyperpc.ae

hyperpc.com

Similar names

pcypher.com

pchyper.com

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
by	dns1.tld.becloudby.com, dns2.tld.becloudby.tech, dns3.tld.becloudby.tech, dns4.tld.becloudby.tech...	9 records
hyperpc.by	ns1.hoster.by, ns2.hoster.by	-

✅ Authoritative Response

Server: 185.179.82.104

NS records: ns1.hoster.by, ns2.hoster.by

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hyperpc.by (unsigned zone)

⏱️ Timing

Total: 1155ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`93.125.99.120`
AAAA	1	`2a0a:7d80:1:7::109:3c1`
NS	2	`ns1.hoster.by, ns2.hoster.by`
MX	1	`mx.yandex.net (pri: 10)`
TXT	3	`v=spf1 +a +mx include:_spf.hoster.by ~al, v=spf1 redirect=_spf.yandex.net...`
SOA	1	`ns1.hoster.by root.vh109.hoster.by`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (dns1.tld.becloudby.com, dns1.tld.becloudby.com, dns2.tld.becloudby.tech...)

AI analysis

hyperpc.by resolves to two IP numbers: 2a0a:7d80:1:7::109:3c1 and 93.125.99.120.

other host names including tuz.by, cubic.by, napoly.by, alfalot.by and sxda.by share IP numbers with hyperpc.by.

hyperpc.by is delegated to two name servers ns1.hoster.by and ns2.hoster.by.

hyperpc.by shares the same name server setup as other domains, for instance xstar.by, goldenmile.biz, ilkomgroup.by, shirma.by and bsa.by.

hyperpc.by at least partially shares name servers with other domains, for instance 107.by.

Host names with two IP numbers:

The host name ns1.hoster.by points to 2a0a:7d80:1:1::6:0 and 93.125.30.200; the host name ns2.hoster.by points to 2a0a:7d80:3:1::8 and 185.179.82.104.

hyperpc.by is handled by a single mail server, mx.yandex.net.

hyperpc.by shares the same mail server setup as other domains, for instance form-a.ru, kube.ru, www.webeffector.ru, murattur.com and markuteri.com.

hyperpc.by shares at least some mail servers with other domains, including datatime.net, fadina.net, remm.by and snt-severnoe.su.

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

hyperpc.by - robtex.com

hyperpc.by

by