owlservermonitor.com - dns.ninja

`owlservermonitor.com`

DNSSEC	⚠️ Not signed
A	112.220.149.73^{🇰🇷 DACOM-NET112.216.0.0/13 contact noc@lgdacom.net if necessary}
NS	`owlservermonitor.com` ⭐
		A	112.220.149.73^{🇰🇷 DACOM-NET112.216.0.0/13 contact noc@lgdacom.net if necessary}
NS	`ns1.cafe24.co.kr` ⚠️ Not in parent delegation
		A	112.175.246.232^{🇰🇷 KT-NET112.168.0.0/13}
			PTR	`gjit.kr`
			PTR	`snoweb.kr`
			PTR	`sinc2030.co.kr`
		A	112.175.246.233^{🇰🇷 KT-NET112.168.0.0/13}
		A	175.125.93.136^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.137^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns1.cafe24.com` ⚠️ Not in parent delegation
		A	112.175.246.230^{🇰🇷 KT-NET112.168.0.0/13}
		A	112.175.246.231^{🇰🇷 KT-NET112.168.0.0/13}
		A	116.126.143.242^{🇰🇷 SKB-NET116.126.0.0/16 SK Broadband}
		A	175.125.93.134^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.135^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns1.cafe24dns.co.kr` ⚠️ Not in zone NS records
		A	175.125.93.196^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns2.cafe24.co.kr` ⚠️ Not in parent delegation
		A	112.175.247.232^{🇰🇷 KT-NET112.168.0.0/13}
			PTR	`snoweb.kr`
			PTR	`sarchi.co.kr`
		A	112.175.247.233^{🇰🇷 KT-NET112.168.0.0/13}
		A	175.125.93.146^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.147^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns2.cafe24.com` ⚠️ Not in parent delegation
		A	1.226.85.4^{🇰🇷 SKB-NET1.224.0.0/13 auto-generated route object for 1.224.0.0/13}
		A	1.234.0.4^{🇰🇷 SKB-NET1.232.0.0/13 auto-generated route object for 1.232.0.0/13}
		A	112.175.11.4^{🇰🇷 KT-NET112.168.0.0/13}
		A	112.175.12.4^{🇰🇷 KT-NET112.168.0.0/13}
NS	`ns3.cafe24dns.co.kr` ⚠️ Not in zone NS records
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁶⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹¹⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
SOA	`owlservermonitor.com`postmaster@owlservermonitor.com serial=20180802

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

NS for

owlservermonitor.com

Same first word

owlservermonitor.com

DNS History

14 records (13 active, 1 former)

●NSns1.cafe24.co.kr2018-08-03 → 2026-07-26 · 2 obs

● 2018-08-03 05:00:56
● 2026-07-26 23:34:42

●NSns1.cafe24.com2018-08-03 → 2026-07-26 · 2 obs

● 2018-08-03 05:00:56
● 2026-07-26 23:34:42

●NSns1.cafe24dns.co.kr2026-04-25 → 2026-07-26 · 3 obs

○ 2018-08-03 05:00:56
● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●NSns2.cafe24.co.kr2018-08-03 → 2026-07-26 · 2 obs

● 2018-08-03 05:00:56
● 2026-07-26 23:34:42

●NSns2.cafe24.com2018-08-03 → 2026-07-26 · 2 obs

● 2018-08-03 05:00:56
● 2026-07-26 23:34:42

●NSns3.cafe24dns.co.kr2026-04-25 → 2026-07-26 · 3 obs

○ 2018-08-03 05:00:56
● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●NSowlservermonitor.com2018-08-03 → 2026-07-26 · 2 obs

● 2018-08-03 05:00:56
● 2026-07-26 23:34:42

●MXalt1.aspmx.l.google.com2026-04-25 → 2026-07-26 · 2 obs

● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●MXalt2.aspmx.l.google.com2026-04-25 → 2026-07-26 · 2 obs

● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●MXalt3.aspmx.l.google.com2026-04-25 → 2026-07-26 · 2 obs

● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●MXalt4.aspmx.l.google.com2026-04-25 → 2026-07-26 · 2 obs

● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●MXaspmx.l.google.com2026-04-25 → 2026-07-26 · 2 obs

● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

●A112.220.149.732026-04-25 → 2026-07-26 · 3 obs

○ 2018-08-03 05:00:56
● 2026-04-25 01:26:20
● 2026-07-26 23:34:42

○A121.190.213.2062018-08-03 → 2018-08-03 · 3 obs

● 2018-08-03 05:00:56
○ 2026-04-25 01:26:20
○ 2026-07-26 23:34:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
owlservermonitor.com	ns1.cafe24dns.co.kr, ns3.cafe24dns.co.kr	-

✅ Authoritative Response

Server:175.125.93.196

NS records: ns1.cafe24dns.co.kr, ns3.cafe24dns.co.kr

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for owlservermonitor.com (unsigned zone)

⏱️ Timing

Total: 1270ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`112.220.149.73`
NS	4	`ns2.cafe24.co.kr, ns2.cafe24.com...`
MX	5	`ASPMX.L.GOOGLE.com (pri: 1), ALT2.ASPMX.L.GOOGLE.com (pri: 6)...`
SOA	1	`owlservermonitor.com postmaster.owlserve`

Analysis

Name Server Role

owlservermonitor.com has owlservermonitor.com as one of its name servers, making it self-hosted for DNS delegation.

Together with owlservermonitor.com, the hosts ns1.cafe24.com, ns2.cafe24.com and ns1.cafe24.co.kr are frequently configured as name servers.

IP Addresses

owlservermonitor.com directs to one IP number, which is 112.220.149.73.

Name Servers

owlservermonitor.com is authoritative under 7 name servers: owlservermonitor.com, ns1.cafe24.com, ns2.cafe24.com and 4 more.

owlservermonitor.com partially shares its NS delegation with several other domains, including soko.co.kr, flyingscent.com, sejongsusan.com and two others.

In DNS configurations, these name servers often share authority with ns2.cafe24.co.kr, ns1.cafe24dns.co.kr, ns3.cafe24dns.co.kr and 6 other name servers.

Hostnames that point to five IP numbers:

ns1.cafe24.com directs to 112.175.246.230, 112.175.246.231, 116.126.143.242 and two other IP addresses.

Hosts pointing to four IP addresses:

ns2.cafe24.com maps to the following IP addresses: 1.226.85.4, 1.234.0.4, 112.175.11.4 and 112.175.12.4.

ns1.cafe24.co.kr maps to the following IP addresses: 112.175.246.232, 112.175.246.233, 175.125.93.136 and 175.125.93.137.

ns2.cafe24.co.kr maps to the following IP addresses: 112.175.247.232, 112.175.247.233, 175.125.93.146 and 175.125.93.147.

Hosts that resolve to one IP address:

owlservermonitor.com points to 112.220.149.73.

ns1.cafe24dns.co.kr points to 175.125.93.196.

Mail Servers

Mail for owlservermonitor.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

owlservermonitor.com shares at least some of its mail servers with other domains — for example thevelocitywave.com, helenbrougham.com.au, franchiseball.com and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com points to 64.233.180.26 and 2607:f8b0:4004:c06::1a.

alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1a.