`reinforcingmen.com`

DNSSEC	⚠️ Not signed
A	209.59.171.131^{🇺🇸 LiquidWeb209.59.128.0/18 Liquid Web Inc 4210 S. Creyts Rd Lansing, MI 48917}
		PTR	`host.johnblenkhorn.com`
NS	`ns1.liquidweb.com` ⭐
		A	2607:fad0:0:8927::a^{🇺🇸 LiquidWeb2607:fad0::/48 Vultr Customer Route}
		A	69.16.223.254^{🇺🇸 LiquidWeb69.16.222.0/23 Liquidweb Inc}
			PTR	`ns1.liquidweb.com`
NS	`ns.liquidweb.com`
		A	2607:fad0:0:8917::a^{🇺🇸 LiquidWeb2607:fad0::/48 Vultr Customer Route}
		A	69.16.222.254^{🇺🇸 LiquidWeb69.16.222.0/23 Liquidweb Inc}
			PTR	`ns.liquidweb.com`
MX	`reinforcingmen.com` ⭐
		A	209.59.171.131^{🇺🇸 LiquidWeb209.59.128.0/18 Liquid Web Inc 4210 S. Creyts Rd Lansing, MI 48917}
			PTR	`host.johnblenkhorn.com`
TXT	`v=spf1 a mx include:spf.sendinblue.com include:send.aweber.com ip4:67.225.133...`
TXT	`Sendinblue-code:c602441b7acd3f8f3954c9e97320447c`
TXT	`yandex-verification: 1a1f51ae3bae1626`
TXT	`google-site-verification=BK2zPujFomWMHLFysc4rusDxZqD76ypA9SFxmEpiVCY`
SOA	`ns.liquidweb.com`admin@liquidweb.com 2025-01-03 #1

`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=1776119252

MX for

reinforcingmen.com

Same first word

reinforcingmen.com

DNS History

4 records (4 active, 0 former)

●NSns.liquidweb.com2026-04-13 → 2026-04-13 · 2 obs

● 2026-04-13 22:46:48
● 2026-04-13 22:46:50

●NSns1.liquidweb.com2026-04-13 → 2026-04-13 · 2 obs

● 2026-04-13 22:46:48
● 2026-04-13 22:46:50

●MXreinforcingmen.com2026-04-13 → 2026-04-13 · 2 obs

● 2026-04-13 22:46:48
● 2026-04-13 22:46:50

●A209.59.171.1312026-04-13 → 2026-04-13 · 2 obs

● 2026-04-13 22:46:48
● 2026-04-13 22:46:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, i.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net...	-
reinforcingmen.com	ns.liquidweb.com, ns1.liquidweb.com	2 records

✅ Authoritative Response

Server:69.16.223.254

NS records: ns.liquidweb.com, ns1.liquidweb.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for reinforcingmen.com (unsigned zone)

⏱️ Timing

Total: 111ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`209.59.171.131`
NS	2	`ns1.liquidweb.com, ns.liquidweb.com`
MX	1	`reinforcingmen.com (pri: 10)`
TXT	4	`yandex-verification: 1a1f51ae3bae1626, google-site-verification=BK2zPujFomWMHLF...`
SOA	1	`ns.liquidweb.com admin.liquidweb.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns.liquidweb.com, ns1.liquidweb.com)

Analysis

Mail Server Role

The mail server for reinforcingmen.com is reinforcingmen.com.

IP Addresses

reinforcingmen.com points to a single IP address: 209.59.171.131.

Name Servers

Two name servers ns1.liquidweb.com and ns.liquidweb.com handle the delegation for reinforcingmen.com.

reinforcingmen.com shares the same name server setup as other domains, for example humagna.com, rezsupport.net, rextopia.com, locksmith24x7.com and muellerworldwide.com.

reinforcingmen.com at least partially shares name servers with other domains, for example design-cosmics.com, tappingsolutionfoundation.org, loudbaby.us, savvyonlineadvertising.com and morgansupplies.com.

These name servers are often used together with ns1.sourcedns.com and ns.sourcedns.com.

Host names with two IP numbers:

ns1.liquidweb.com points to 2607:fad0:0:8927::a and 69.16.223.254.

ns.liquidweb.com points to 2607:fad0:0:8917::a and 69.16.222.254.

Mail Servers

One mail server handles reinforcingmen.com; that server is reinforcingmen.com.

reinforcingmen.com points to a single IP number: 209.59.171.131.

reinforcingmen.com - robtex.com