`regardinghorses.com`

DNSSEC	⚠️ Not signed
A	3.114.75.152^{🇯🇵 Amazon3.112.0.0/14 EC2 NRT prefix}
		PTR	`ec2-3-114-75-152.ap-northeast-1.compute.amazonaws.com`
NS	`dns-auth.quicca.com` ⭐
		A	35.200.82.39^{🇯🇵 Google35.200.80.0/20}
			PTR	`39.82.200.35.bc.googleusercontent.com`
NS	`ns1.quedomain.com`
		A	35.200.107.200^{🇯🇵 Google35.200.96.0/20}
			PTR	`200.107.200.35.bc.googleusercontent.com`
NS	`ns2.quedomain.com`
		A	35.200.0.91^{🇯🇵 Google35.200.0.0/20}
			PTR	`91.0.200.35.bc.googleusercontent.com`
NS	`ns3.quedomain.com`
		A	35.200.26.89^{🇯🇵 Google35.200.16.0/20}
			PTR	`89.26.200.35.bc.googleusercontent.com`
SOA	`dns-auth.quicca.com`hostmaster@regardinghorses.com 2019-08-21 #2

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

Same first word

regardinghorses.com

DNS History

9 records (5 active, 4 former)

●NSdns-auth.quicca.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-04-18 22:11:28
● 2026-03-25 20:15:14

○NSns1.bluehost.com2015-06-24 → 2017-04-18 · 3 obs

● 2015-06-24 07:26:04
● 2017-04-18 22:11:28
○ 2026-03-25 20:15:14

●NSns1.quedomain.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-04-18 22:11:28
● 2026-03-25 20:15:14

○NSns2.bluehost.com2015-06-24 → 2017-04-18 · 3 obs

● 2015-06-24 07:26:04
● 2017-04-18 22:11:28
○ 2026-03-25 20:15:14

●NSns2.quedomain.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-04-18 22:11:28
● 2026-03-25 20:15:14

●NSns3.quedomain.com2026-03-25 → 2026-03-25 · 2 obs

○ 2017-04-18 22:11:28
● 2026-03-25 20:15:14

○MXregardinghorses.com2015-06-24 → 2017-04-18 · 3 obs

● 2015-06-24 07:26:04
● 2017-04-18 22:11:28
○ 2026-03-25 20:15:14

●A3.114.75.1522026-03-25 → 2026-03-25 · 2 obs

○ 2017-04-18 22:11:28
● 2026-03-25 20:15:14

○A66.147.244.1732015-06-24 → 2017-04-18 · 3 obs

● 2015-06-24 07:26:04
● 2017-04-18 22:11:28
○ 2026-03-25 20:15:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
regardinghorses.com	ns1.quedomain.com, ns2.quedomain.com, ns3.quedomain.com	3 records

✅ Authoritative Response

Server:35.200.107.200

NS records: ns1.quedomain.com, ns2.quedomain.com, ns3.quedomain.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for regardinghorses.com (unsigned zone)

⏱️ Timing

Total: 368ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.114.75.152`
NS	3	`ns3.quedomain.com, ns1.quedomain.com...`
SOA	1	`dns-auth.quicca.com hostmaster.regarding`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.quedomain.com, ns2.quedomain.com, ns3.quedomain.com)

Analysis

IP Addresses

regardinghorses.com points to an IP address: 3.114.75.152.

other host names, for instance bographik.com, btteuskadi.net, www.bographik.com and ec2-3-114-75-152.ap-northeast-1.compute.amazonaws.com share IP numbers with regardinghorses.com.

Name Servers

regardinghorses.com delegates to four name servers: ns1.quedomain.com, ns2.quedomain.com, ns3.quedomain.com and dns-auth.quicca.com.

regardinghorses.com at least partially shares name servers with other domains, for instance tachikawa-ya.com, a-deg.com, otenki.co, matsuoka-pro.com and assistad-sys.jp.

These name servers are commonly used with the following: a.misconfigured.dns.server.invalid, ns1.quicca-plus.com, ns2.quicca-plus.com and ns3.quicca-plus.com.

Host names with one IP number: ns1.quedomain.com points to: 35.200.107.200; ns2.quedomain.com points to: 35.200.0.91; ns3.quedomain.com points to: 35.200.26.89; dns-auth.quicca.com points to: 35.200.82.39.

regardinghorses.com - robtex.com