`doubletreekyoto.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 2023-05-16 #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=1785648602

Same first word

doubletreekyoto.jp

DNS History

8 records (8 active, 0 former)

●NSns1.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●NSns2.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●NSns3.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●NSns4.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●NSns5.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●NSns6.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●NSns7.markmonitor.com2026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

●A167.187.200.182026-07-27 → 2026-08-02 · 2 obs

● 2026-07-27 12:36:00
● 2026-08-02 06:06:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp...	-
doubletreekyoto.jp	ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com...	-

✅ Authoritative Response

Server:149.112.161.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for doubletreekyoto.jp (unsigned zone)

⏱️ Timing

Total: 926ms | Queries: -

📄 Records

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

Analysis

IP Addresses

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

Two other host names, along with graduatebatonrouge.com, hgisantamarta.com and philadelphiacityavenue.hilton.com, also share IP numbers with doubletreekyoto.jp.

Name Servers

doubletreekyoto.jp has 7 name servers — ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.

At least some of doubletreekyoto.jp's name servers are shared with other domains, for example xn--ditkarma-jtb4l.com, metlifeduathlon.com, dollar.lu and two more.

These name servers are often deployed together 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 resolves to 149.112.160.1 and 2620:10a:80a8::1.

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

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

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

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

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

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