`richmondhoarding.com`

DNSSEC	⚠️ Not signed
A	162.159.134.42^{Cloudflare162.159.128.0/19 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns03.domaincontrol.com` ⭐
		A	2603:5:2150::2^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns03.domaincontrol.com`
		A	97.74.101.2^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns03.domaincontrol.com`
NS	`ns04.domaincontrol.com`
		A	2603:5:2250::2^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns04.domaincontrol.com`
		A	173.201.69.2^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns04.domaincontrol.com`
MX	`richmondhoarding-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c91d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::5^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch4pr21cu00105.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr03cu00403.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn1pr21cu00100.inbound.protection.outlook.com`
		A	52.101.9.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00400.inbound.protection.outlook.com`
		A	52.101.10.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr21cu00204.inbound.protection.outlook.com`
		A	52.101.11.9^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr02cu00101.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
TXT	`MS=ms17114136`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`ca3-c16875908b5f43a4b1e4b8d13d2e55e1`
SOA	`ns03.domaincontrol.com`dns@jomax.net 2024-07-18 #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=1776214977

Same first word

richmondhoarding.com

DNS History

13 records (4 active, 9 former)

●NSns03.domaincontrol.com2018-09-03 → 2026-04-15 · 2 obs

● 2018-09-03 06:51:10
● 2026-04-15 01:05:18

●NSns04.domaincontrol.com2018-09-03 → 2026-04-15 · 2 obs

● 2018-09-03 06:51:10
● 2026-04-15 01:05:18

●MXrichmondhoarding-com.mail.protection.outlook.com2026-03-09 → 2026-04-15 · 2 obs

● 2026-03-09 21:59:32
● 2026-04-15 01:05:18

●A162.159.134.422026-03-09 → 2026-04-15 · 3 obs

○ 2018-09-03 06:51:10
● 2026-03-09 21:59:32
● 2026-04-15 01:05:18

○A184.168.221.382018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A184.168.221.412018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A184.168.221.542018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A50.63.202.362018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A50.63.202.402018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A50.63.202.472018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A50.63.202.502018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A50.63.202.512018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

○A50.63.202.542018-09-03 → 2018-09-03 · 3 obs

● 2018-09-03 06:51:10
○ 2026-03-09 21:59:32
○ 2026-04-15 01:05:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, e.gtld-servers.net...	-
richmondhoarding.com	ns03.domaincontrol.com, ns04.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.69.2

NS records: ns03.domaincontrol.com, ns04.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for richmondhoarding.com (unsigned zone)

⏱️ Timing

Total: 142ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.159.134.42`
NS	2	`ns03.domaincontrol.com, ns04.domaincontrol.com`
MX	1	`richmondhoarding-com.mail.protection.out`
TXT	3	`MS=ms17114136, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`ns03.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns03.domaincontrol.com, ns03.domaincontrol.com, ns04.domaincontrol.com...)

Analysis

IP Addresses

richmondhoarding.com points to IP number 162.159.134.42.

For instance, other host names brixtonforged.com, host.buffalorock.com, huffmansauto.com, monroevillepa.com and thecoolestservice.com share IP numbers with richmondhoarding.com.

Name Servers

richmondhoarding.com is delegated to two name servers: ns03.domaincontrol.com and ns04.domaincontrol.com.

richmondhoarding.com uses the same name server setup as other domains such as intertek-solutions.com, 100percentgroup.com, redpixel.me, ulti-ski.com and nyvideomarketingagency.com.

Host names with two IP numbers:

ns03.domaincontrol.com points to 2603:5:2150::2 and 97.74.101.2; ns04.domaincontrol.com points to 2603:5:2250::2 and 173.201.69.2.

Mail Servers

richmondhoarding.com is handled by a single mail server, richmondhoarding-com.mail.protection.outlook.com.

Host name richmondhoarding-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c91d::, 2a01:111:f403:c946::5, 2a01:111:f403:f804::3, 2a01:111:f403:f908::, 52.101.9.24, 52.101.10.12, 52.101.11.9 and 52.101.11.15.

richmondhoarding.com - robtex.com