`doubletreespa.jp`

DNSSEC	⚠️ Not signed
A	167.187.200.18^{🇺🇸 AS26529167.187.200.0/22 AC_HILTONWORL}
		PTR	`ftcrdf-nonsecure.hilton.com`
		PTR	`richardsondallas.hilton.com`
		PTR	`uksupply.hilton.com`
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com`
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com`
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2024-07-23 #1

`jp`

	DNSSEC	🔒 Signed (DS record present)
	NS	`z.dns.jp` ⭐
	NS	`a.dns.jp`
	NS	`b.dns.jp`
	NS	`c.dns.jp`
	NS	`d.dns.jp`
	NS	`e.dns.jp`
	NS	`f.dns.jp`
	NS	`g.dns.jp`
	NS	`h.dns.jp`
	SOA	`z.dns.jp`root@dns.jp serial=1785946502

Same first word

DNS History

13 records (8 active, 5 former)

○NSns1.chrl.twtelecom.net2015-07-05 → 2017-03-26 · 4 obs

● 2015-07-05 00:22:46
● 2017-03-26 09:32:48
○ 2020-02-09 19:21:24
○ 2026-08-05 16:37:36

●NSns1.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

○NSns1.nycl.twtelecom.net2015-07-05 → 2017-03-26 · 4 obs

● 2015-07-05 00:22:46
● 2017-03-26 09:32:48
○ 2020-02-09 19:21:24
○ 2026-08-05 16:37:36

●NSns2.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

○NSns3.level3.net2020-02-09 → 2020-02-09 · 4 obs

○ 2017-03-26 09:32:48
● 2020-02-09 19:21:24
○ 2026-07-27 12:39:40
○ 2026-08-05 16:37:36

●NSns3.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

○NSns4.level3.net2020-02-09 → 2020-02-09 · 4 obs

○ 2017-03-26 09:32:48
● 2020-02-09 19:21:24
○ 2026-07-27 12:39:40
○ 2026-08-05 16:37:36

●NSns4.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

●NSns5.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

●NSns6.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

●NSns7.markmonitor.com2026-07-27 → 2026-08-05 · 3 obs

○ 2020-02-09 19:21:24
● 2026-07-27 12:39:40
● 2026-08-05 16:37:36

●A167.187.200.182020-02-09 → 2026-08-05 · 3 obs

○ 2017-03-26 09:32:48
● 2020-02-09 19:21:24
● 2026-08-05 16:37:36

○A167.187.200.232015-07-05 → 2017-03-26 · 4 obs

● 2015-07-05 00:22:46
● 2017-03-26 09:32:48
○ 2020-02-09 19:21:24
○ 2026-08-05 16:37:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	a.dns.jp, h.dns.jp, g.dns.jp, d.dns.jp...	-
doubletreespa.jp	ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns1.markmonitor.com...	-

✅ Authoritative Response

Server:149.112.160.2

NS records: ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for doubletreespa.jp (unsigned zone)

⏱️ Timing

Total: 1030ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`167.187.200.18`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

Analysis

IP Addresses

doubletreespa.jp resolves to just one IP address, 167.187.200.18.

Two other host names, along with urumqi.hilton.com, hhonors.com.pr and hometosuitesbyhilton.info, also share IP numbers with doubletreespa.jp.

Name Servers

doubletreespa.jp delegates authority to 7 name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com plus 4 other.

There is at least partial name server overlap between doubletreespa.jp and other domains — telegraphtalk.com, mercadoplay.uy, gomabsgo.com and two more among them.

These name servers tend to appear in combination with the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Host names that have two IP addresses:

ns1.markmonitor.com directs traffic to 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com directs traffic to 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com directs traffic to 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com directs traffic to 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com directs traffic to 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com directs traffic to 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com directs traffic to 149.112.161.2 and 2620:10a:80a9::2.