`traveltoseoul.com`

DNSSEC	⚠️ Not signed
A	172.234.24.211^{🇺🇸 AKAMAI-LINODE-AP172.234.16.0/20 Akamai Technologies}
		PTR	`ip-172-234-24-211.defastlink.net`
A	172.239.57.117^{🇺🇸 AKAMAI-LINODE-AP172.239.32.0/19 Akamai Technologies}
NS	`dns101.registrar-servers.com` ⭐
		A	2600:3c02::f03c:93ff:febe:d723^{🇺🇸 AKAMAI-LINODE-AP2600:3c02::/32 Akamai Technologies}
		A	170.187.200.230^{🇺🇸 AKAMAI-LINODE-AP170.187.200.0/21 Akamai Technologies}
			PTR	`latte.parklogic.com`
NS	`dns102.registrar-servers.com`
		A	2600:3c02::f03c:93ff:febe:c249^{🇺🇸 AKAMAI-LINODE-AP2600:3c02::/32 Akamai Technologies}
		A	23.239.17.221^{🇺🇸 AKAMAI-LINODE-AP23.239.16.0/22 Akamai Technologies}
			PTR	`merlot.parklogic.com`
MX	`mx.plingest.com` ⭐
		A	38.143.66.193^{🇺🇸 AS6302338.143.66.0/24 Proxy-registered route object 2011686}
			PTR	`193-66-143-38.clients.gthost.com`
TXT	`v=spf1 -all`
SOA	`dns101.registrar-servers.com`hostmaster@parklogic.com 2021-05-19 #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=1774682437

Same first word

traveltoseoul.com

DNS History

33 records (5 active, 28 former)

○NSdns1.name-services.com2018-01-29 → 2018-01-29 · 3 obs

● 2018-01-29 06:51:24
○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

●NSdns101.registrar-servers.com2026-03-05 → 2026-03-28 · 3 obs

○ 2026-02-24 10:10:18
● 2026-03-05 09:15:18
● 2026-03-28 07:44:16

●NSdns102.registrar-servers.com2026-03-05 → 2026-03-28 · 3 obs

○ 2026-02-24 10:10:18
● 2026-03-05 09:15:18
● 2026-03-28 07:44:16

○NSdns2.name-services.com2018-01-29 → 2018-01-29 · 3 obs

● 2018-01-29 06:51:24
○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○NSdns3.name-services.com2018-01-29 → 2018-01-29 · 3 obs

● 2018-01-29 06:51:24
○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○NSdns4.name-services.com2018-01-29 → 2018-01-29 · 3 obs

● 2018-01-29 06:51:24
○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○NSdns5.name-services.com2018-01-29 → 2018-01-29 · 3 obs

● 2018-01-29 06:51:24
○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○NSns1.dns-parking.com2026-02-17 → 2026-02-24 · 5 obs

○ 2018-01-29 06:51:24
● 2026-02-17 08:30:48
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○NSns2.dns-parking.com2026-02-17 → 2026-02-24 · 5 obs

○ 2018-01-29 06:51:24
● 2026-02-17 08:30:48
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

●MXmx.plingest.com2026-03-05 → 2026-03-28 · 3 obs

○ 2026-02-24 10:10:18
● 2026-03-05 09:15:18
● 2026-03-28 07:44:16

○MXmx1.hostinger.com2026-02-17 → 2026-02-24 · 4 obs

● 2026-02-17 08:30:48
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○MXmx2.hostinger.com2026-02-17 → 2026-02-24 · 4 obs

● 2026-02-17 08:30:48
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○A145.223.124.292026-02-24 → 2026-02-24 · 4 obs

○ 2026-02-21 18:27:12
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○A145.223.124.92026-02-17 → 2026-02-17 · 4 obs

○ 2018-01-29 06:51:24
● 2026-02-17 08:30:48
○ 2026-02-21 18:27:12
○ 2026-03-28 07:44:16

○A147.79.72.1852026-02-21 → 2026-02-21 · 4 obs

○ 2026-02-17 08:30:48
● 2026-02-21 18:27:12
○ 2026-02-24 10:10:18
○ 2026-03-28 07:44:16

○A147.79.72.2262026-02-17 → 2026-03-28 · 2 obs

○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

●A172.234.24.2112026-03-05 → 2026-03-28 · 3 obs

○ 2026-02-24 10:10:18
● 2026-03-05 09:15:18
● 2026-03-28 07:44:16

●A172.239.57.1172026-03-05 → 2026-03-28 · 3 obs

○ 2026-02-24 10:10:18
● 2026-03-05 09:15:18
● 2026-03-28 07:44:16

○A207.148.248.1432015-10-30 → 2017-01-03 · 5 obs

○ 2015-06-15 15:29:24
● 2015-10-30 15:31:38
● 2017-01-03 02:40:28
○ 2018-01-29 06:51:24
○ 2026-03-28 07:44:16

○A2a02:4780:4a:27d6:864:557e:c120:a8692026-02-21 → 2026-02-21 · 4 obs

○ 2026-02-17 08:30:48
● 2026-02-21 18:27:12
○ 2026-02-24 10:10:18
○ 2026-03-28 07:44:16

○A2a02:4780:4a:6e1f:9dac:1db1:cf8a:1f372026-02-24 → 2026-02-24 · 4 obs

○ 2026-02-21 18:27:12
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○A2a02:4780:4a:79f5:9c37:15e8:96ea:f6742026-02-17 → 2026-03-28 · 2 obs

○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○A2a02:4780:4a:f946:42d4:73d:619:3c2b2026-02-17 → 2026-02-17 · 4 obs

○ 2018-01-29 06:51:24
● 2026-02-17 08:30:48
○ 2026-02-21 18:27:12
○ 2026-03-28 07:44:16

○A2a02:4780:4b:34f4:33f8:437:8fbf:5e022026-02-21 → 2026-02-21 · 4 obs

○ 2026-02-17 08:30:48
● 2026-02-21 18:27:12
○ 2026-02-24 10:10:18
○ 2026-03-28 07:44:16

○A2a02:4780:4b:5c4:cdff:40ad:20d9:4e6c2026-02-17 → 2026-03-28 · 2 obs

○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○A2a02:4780:4b:8cd:6538:98cc:e606:95722026-02-17 → 2026-02-17 · 4 obs

○ 2018-01-29 06:51:24
● 2026-02-17 08:30:48
○ 2026-02-21 18:27:12
○ 2026-03-28 07:44:16

○A2a02:4780:4c:7523:620c:910:548d:4de62026-02-24 → 2026-02-24 · 4 obs

○ 2026-02-21 18:27:12
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○A66.151.181.492015-06-15 → 2015-06-15 · 3 obs

● 2015-06-15 15:29:24
○ 2015-10-30 15:31:38
○ 2026-03-28 07:44:16

○A69.64.147.382018-01-29 → 2018-01-29 · 4 obs

○ 2017-01-03 02:40:28
● 2018-01-29 06:51:24
○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○A88.223.87.1112026-02-24 → 2026-02-24 · 4 obs

○ 2026-02-21 18:27:12
● 2026-02-24 10:10:18
○ 2026-03-05 09:15:18
○ 2026-03-28 07:44:16

○A88.223.87.1992026-02-21 → 2026-02-21 · 4 obs

○ 2026-02-17 08:30:48
● 2026-02-21 18:27:12
○ 2026-02-24 10:10:18
○ 2026-03-28 07:44:16

○A88.223.87.2272026-02-17 → 2026-03-28 · 2 obs

○ 2026-02-17 08:30:48
○ 2026-03-28 07:44:16

○A88.223.87.632026-02-17 → 2026-02-17 · 4 obs

○ 2018-01-29 06:51:24
● 2026-02-17 08:30:48
○ 2026-02-21 18:27:12
○ 2026-03-28 07:44:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net...	-
traveltoseoul.com	dns101.registrar-servers.com, dns102.registrar-servers.com	4 records

✅ Authoritative Response

Server:170.187.200.230

NS records: dns101.registrar-servers.com, dns102.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for traveltoseoul.com (unsigned zone)

⏱️ Timing

Total: 173ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.234.24.211, 172.239.57.117`
NS	2	`dns101.registrar-servers.com, dns102.registrar-servers.com`
MX	1	`mx.plingest.com (pri: 10)`
TXT	1	`v=spf1 -all`
SOA	1	`dns101.registrar-servers.com hostmaster.`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns101.registrar-servers.com, dns101.registrar-servers.com, dns102.registrar-servers.com...)

Analysis

IP Addresses

traveltoseoul.com points to two IP numbers: 172.234.24.211 and 172.239.57.117.

Other host names, for instance axiomly.com, flykthy.com, spainmakes.com, sofia-invest.com and mail.gohostam.com share IP numbers with traveltoseoul.com.

Name Servers

traveltoseoul.com is delegated to two name servers: dns101.registrar-servers.com and dns102.registrar-servers.com.

traveltoseoul.com uses the same name server setup as other domains, for instance mail.almasriaco.com, mx.blackrockpage.org, akbpg.com, bigamyc.uno and shahroozhost.com.

traveltoseoul.com partially shares name servers with other domains, for instance vorbuildhomes.com.

Host names with two IP numbers:

The host dns101.registrar-servers.com points to 2600:3c02::f03c:93ff:febe:d723 and 170.187.200.230.

The host dns102.registrar-servers.com points to 2600:3c02::f03c:93ff:febe:c249 and 23.239.17.221.

Mail Servers

The mail server for traveltoseoul.com is mx.plingest.com.

traveltoseoul.com shares the same mail server setup as other domains, including deborahemmanuel.com, *.mylivecricket.tv, com.sgwww.articlerw.com, 4phoneaccessories.com and medcoreship.com.

Host name mx.plingest.com resolves to IP 38.143.66.193.

traveltoseoul.com - robtex.com