`bleedingtree.com`

DNSSEC	⚠️ Not signed
A	158.106.134.135^{🇺🇸 PRIVATESYSTEMS158.106.132.0/22 PrivateSystems Networks GA}
		PTR	`host.bleedingtree.com`
NS	`ns1.bleedingtree.com` ⭐
		A	158.106.134.135^{🇺🇸 PRIVATESYSTEMS158.106.132.0/22 PrivateSystems Networks GA}
			PTR	`host.bleedingtree.com`
NS	`ns2.bleedingtree.com`
		A	158.106.134.136^{🇺🇸 PRIVATESYSTEMS158.106.132.0/22 PrivateSystems Networks GA}
MX	`bleedingtree.com` ⭐
		A	158.106.134.135^{🇺🇸 PRIVATESYSTEMS158.106.132.0/22 PrivateSystems Networks GA}
			PTR	`host.bleedingtree.com`
TXT	`v=spf1 a mx ip4:158.106.134.135 ~all`
TXT	`MS=ms20411360`
SOA	`ns1.bleedingtree.com`dns@bleedingtree.com 2024-03-08 #0

`com`

	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=1776983296

WOT: UNKNOWN (61/100)

MX for

bleedingtree.com

Subdomains

ns3.bleedingtree.com

ns2.bleedingtree.com

host.bleedingtree.com

ns4.bleedingtree.com

ns1.bleedingtree.com

Same first word

bleedingtree.com

DNS History

5 records (4 active, 1 former)

●NSns1.bleedingtree.com2015-06-18 → 2026-04-23 · 2 obs

● 2015-06-18 03:20:46
● 2026-04-23 22:32:38

●NSns2.bleedingtree.com2015-06-18 → 2026-04-23 · 2 obs

● 2015-06-18 03:20:46
● 2026-04-23 22:32:38

●MXbleedingtree.com2026-02-18 → 2026-04-23 · 2 obs

● 2026-02-18 00:49:10
● 2026-04-23 22:32:38

●A158.106.134.1352026-02-18 → 2026-04-23 · 3 obs

○ 2017-04-04 22:44:48
● 2026-02-18 00:49:10
● 2026-04-23 22:32:38

○A162.253.34.192015-06-18 → 2017-04-04 · 4 obs

● 2015-06-18 03:20:46
● 2017-04-04 22:44:48
○ 2026-02-18 00:49:10
○ 2026-04-23 22:32:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
bleedingtree.com	ns1.bleedingtree.com, ns2.bleedingtree.com	2 records

✅ Authoritative Response

Server:158.106.134.135

NS records: ns1.bleedingtree.com, ns2.bleedingtree.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bleedingtree.com (unsigned zone)

⏱️ Timing

Total: 149ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`158.106.134.135`
NS	2	`ns2.bleedingtree.com, ns1.bleedingtree.com`
MX	1	`bleedingtree.com (pri: 10)`
TXT	2	`v=spf1 a mx ip4:158.106.134.135 ~all, MS=ms20411360`
SOA	1	`ns1.bleedingtree.com dns.bleedingtree.co`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.bleedingtree.com, ns2.bleedingtree.com)

Analysis

Hierarchy

bleedingtree.com is a parent of ns3.bleedingtree.com, ns2.bleedingtree.com, host.bleedingtree.com, ns4.bleedingtree.com and ns1.bleedingtree.com.

Mail Server Role

For bleedingtree.com, the mail server is bleedingtree.com.

IP Addresses

bleedingtree.com points to a single IP number: 158.106.134.135.

other host names for instance mail.host.bleedingtree.com, ns3.bleedingtree.com, _dc-mx.29f591209b54.happybulletin.com, host.bleedingtree.com and _dc-mx.4d001e75358d.mynameisrush.com share IP numbers with bleedingtree.com.

Name Servers

bleedingtree.com is delegated to two name servers: ns1.bleedingtree.com and ns2.bleedingtree.com.

bleedingtree.com shares the same name server setup as other domains, for example host.bleedingtree.com and onlinechurchbulletin.com.

Host names with one IP number:

The host ns1.bleedingtree.com points to 158.106.134.135 and the host ns2.bleedingtree.com points to 158.106.134.136.

Mail Servers

One mail server handles bleedingtree.com.

Host name bleedingtree.com points to IP address 158.106.134.135.

bleedingtree.com - robtex.com