`bleedingthreats.net`

DNSSEC	⚠️ Not signed
A	188.165.5.15^{🇫🇷 OVH188.165.0.0/16 ISP Paris, France}
		PTR	`ip15.ip-188-165-5.eu`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@bleedingthreats.net 2026-01-20 #2

`net`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1774572702

Same first word

bleedingthreats.net

DNS History

20 records (3 active, 17 former)

○NSdns10.parkpage.foundationapi.com2015-12-20 → 2015-12-20 · 4 obs

○ 2015-10-10 17:17:14
● 2015-12-20 13:30:38
○ 2016-02-23 12:03:24
○ 2026-03-27 01:03:50

○NSdns9.parkpage.foundationapi.com2015-12-20 → 2015-12-20 · 4 obs

○ 2015-10-10 17:17:14
● 2015-12-20 13:30:38
○ 2016-02-23 12:03:24
○ 2026-03-27 01:03:50

○NSf1g1ns1.dnspod.net2015-05-17 → 2015-10-10 · 4 obs

● 2015-05-17 22:11:46
● 2015-10-10 17:17:14
○ 2015-12-20 13:30:38
○ 2026-03-27 01:03:50

○NSf1g1ns2.dnspod.net2015-05-17 → 2015-05-17 · 3 obs

● 2015-05-17 22:11:46
○ 2015-12-20 13:30:38
○ 2026-03-27 01:03:50

●NSns1.dyna-ns.net2026-03-27 → 2026-03-27 · 3 obs

○ 2020-01-13 00:58:24
● 2026-03-27 01:03:46
● 2026-03-27 01:03:50

○NSns1.xserver.jp2016-02-23 → 2017-02-01 · 5 obs

○ 2015-12-20 13:30:38
● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

●NSns2.dyna-ns.net2026-03-27 → 2026-03-27 · 3 obs

○ 2020-01-13 00:58:24
● 2026-03-27 01:03:46
● 2026-03-27 01:03:50

○NSns2.xserver.jp2016-02-23 → 2017-02-01 · 5 obs

○ 2015-12-20 13:30:38
● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

○NSns3.xserver.jp2016-02-23 → 2017-02-01 · 5 obs

○ 2015-12-20 13:30:38
● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

○NSns4.xserver.jp2016-02-23 → 2017-02-01 · 5 obs

○ 2015-12-20 13:30:38
● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

○NSns5.xserver.jp2016-02-23 → 2017-02-01 · 5 obs

○ 2015-12-20 13:30:38
● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

○NSuns01.lolipop.jp2020-01-13 → 2020-01-13 · 4 obs

○ 2017-02-01 00:13:58
● 2020-01-13 00:58:24
○ 2026-03-27 01:03:46
○ 2026-03-27 01:03:50

○NSuns02.lolipop.jp2020-01-13 → 2020-01-13 · 4 obs

○ 2017-02-01 00:13:58
● 2020-01-13 00:58:24
○ 2026-03-27 01:03:46
○ 2026-03-27 01:03:50

○MXbleedingthreats.net2016-02-23 → 2017-02-01 · 4 obs

● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

○MXmx01.lolipop.jp2020-01-13 → 2020-01-13 · 4 obs

○ 2017-02-01 00:13:58
● 2020-01-13 00:58:24
○ 2026-03-27 01:03:46
○ 2026-03-27 01:03:50

○A157.7.107.392020-01-13 → 2020-01-13 · 4 obs

○ 2017-02-01 00:13:58
● 2020-01-13 00:58:24
○ 2026-03-27 01:03:46
○ 2026-03-27 01:03:50

●A188.165.5.152026-03-27 → 2026-03-27 · 3 obs

○ 2020-01-13 00:58:24
● 2026-03-27 01:03:46
● 2026-03-27 01:03:50

○A209.99.40.2232015-12-20 → 2015-12-20 · 4 obs

○ 2015-05-17 22:11:46
● 2015-12-20 13:30:38
○ 2016-02-23 12:03:24
○ 2026-03-27 01:03:50

○A210.188.201.1642016-02-23 → 2017-02-01 · 5 obs

○ 2015-12-20 13:30:38
● 2016-02-23 12:03:24
● 2017-02-01 00:13:58
○ 2020-01-13 00:58:24
○ 2026-03-27 01:03:50

○A43.251.228.442015-05-17 → 2015-05-17 · 3 obs

● 2015-05-17 22:11:46
○ 2015-12-20 13:30:38
○ 2026-03-27 01:03:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bleedingthreats.net	ns2.dyna-ns.net, ns1.dyna-ns.net	4 records

✅ Authoritative Response

Server:162.159.25.5

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bleedingthreats.net (unsigned zone)

⏱️ Timing

Total: 195ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`188.165.5.15`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.bleedingthrea`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns2.dyna-ns.net, ns2.dyna-ns.net, ns1.dyna-ns.net...)

Analysis

IP Addresses

bleedingthreats.net resolves to a single IP address: 188.165.5.15.

Other host names including moldmakingchina.com, microsoftcustomersupport-number.com, ns2.moldmakingchina.com, nuche.org and ip15.ip-188-165-5.eu share IP numbers with bleedingthreats.net.

Name Servers

bleedingthreats.net's delegation uses two name servers, ns1.dyna-ns.net and ns2.dyna-ns.net.

bleedingthreats.net shares the same name server setup as other domains, for example kisa.si, bayareadates.com, exaship.com, sequrechat.com and xn--nima-uoa.com.

Host names with four IP numbers:

ns1.dyna-ns.net points to 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158.

ns2.dyna-ns.net points to 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.

bleedingthreats.net - robtex.com