inalize.com - dns.ninja

`inalize.com`

DNSSEC	⚠️ Not signed
A	2a02:2350:5:10b:80c8:b32c:67e4:c0ce^{🇩🇰 ONECOM2a02:2350::/32 One.com A/S}
A	46.30.213.121^{🇩🇰 ONECOM46.30.208.0/21 One.com A/S}
NS	`ns01.one.com` ⭐
		A	2001:67c:28cc::10^{ONECOM-INFRA2001:67c:28cc::/48}
			PTR	`ns01.one.com`
		A	195.206.121.10^{ONECOM-INFRA195.206.121.0/24}
			PTR	`ns01.one.com`
NS	`ns02.one.com`
		A	2001:67c:3c0::10^{🇩🇰 ONECOM2001:67c:3c0::/48}
			PTR	`ns02.one.com`
		A	185.10.11.10^{ONECOM185.10.11.0/24}
			PTR	`ns02.one.com`
MX	`mx1.pub.mailpod10-cph3.one.com` ⭐
		A	104.37.34.70^{🇩🇰 ONECOM104.37.32.0/21 One.com A/S}
			PTR	`mx1.pub.mailpod10-cph3.one.com`
MX	`mx2.pub.mailpod10-cph3.one.com` ⭐
		A	104.37.34.71^{🇩🇰 ONECOM104.37.32.0/21 One.com A/S}
			PTR	`mx2.pub.mailpod10-cph3.one.com`
MX	`mx3.pub.mailpod10-cph3.one.com` ⭐
		A	104.37.34.72^{🇩🇰 ONECOM104.37.32.0/21 One.com A/S}
			PTR	`mx3.pub.mailpod10-cph3.one.com`
MX	`mx4.pub.mailpod10-cph3.one.com` ⭐
		A	104.37.34.73^{🇩🇰 ONECOM104.37.32.0/21 One.com A/S}
			PTR	`mx4.pub.mailpod10-cph3.one.com`
SOA	`ns01.one.com`hostmaster@one.com 2026-07-26 #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=1785738202

Same first word

inalize.com

Similar names

zailine.com

zelinia.com

zeliani.com

zailine.net

zeinali.ir

aileniz.net

alinezi.com

lianzie.com

zelinia.net

zeilian.com

alenizi.net

lizanie.pl

lianzei.com

aileniz.com

ezilian.cn

ilizane.dk

linaize.com

aziline.com

lianzei.cn

zielina.com

alenizi.com

nailize.com

zenilia.com

DNS History

15 records (8 active, 7 former)

●NSns01.one.com2026-03-06 → 2026-08-03 · 3 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-08-03 06:36:38

●NSns02.one.com2026-03-06 → 2026-08-03 · 3 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-08-03 06:36:38

○NSns57.domaincontrol.com2016-01-13 → 2017-06-21 · 4 obs

● 2016-01-13 21:10:10
● 2017-06-21 22:29:18
○ 2026-03-06 10:56:52
○ 2026-08-03 06:36:38

○NSns58.domaincontrol.com2016-01-13 → 2017-06-21 · 4 obs

● 2016-01-13 21:10:10
● 2017-06-21 22:29:18
○ 2026-03-06 10:56:52
○ 2026-08-03 06:36:38

○MXmailstore1.secureserver.net2016-01-13 → 2017-06-21 · 4 obs

● 2016-01-13 21:10:10
● 2017-06-21 22:29:18
○ 2026-03-06 10:56:52
○ 2026-08-03 06:36:38

●MXmx1.pub.mailpod10-cph3.one.com2026-03-06 → 2026-08-03 · 3 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-08-03 06:36:38

●MXmx2.pub.mailpod10-cph3.one.com2026-03-06 → 2026-08-03 · 3 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-08-03 06:36:38

●MXmx3.pub.mailpod10-cph3.one.com2026-03-06 → 2026-08-03 · 6 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-04-08 03:29:20
○ 2026-04-23 03:27:44
● 2026-05-01 04:57:24
● 2026-08-03 06:36:38

●MXmx4.pub.mailpod10-cph3.one.com2026-03-06 → 2026-08-03 · 3 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-08-03 06:36:38

○MXsmtp.secureserver.net2016-01-13 → 2017-06-21 · 4 obs

● 2016-01-13 21:10:10
● 2017-06-21 22:29:18
○ 2026-03-06 10:56:52
○ 2026-08-03 06:36:38

●A2a02:2350:5:10b:80c8:b32c:67e4:c0ce2026-04-23 → 2026-08-03 · 3 obs

○ 2026-04-08 03:29:20
● 2026-04-23 03:27:44
● 2026-08-03 06:36:38

○A2a02:2350:5:10b:80f7:d1fd:dd47:d4452026-03-06 → 2026-04-08 · 5 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-04-08 03:29:20
○ 2026-04-23 03:27:44
○ 2026-08-03 06:36:38

●A46.30.213.1212026-04-23 → 2026-08-03 · 3 obs

○ 2026-04-08 03:29:20
● 2026-04-23 03:27:44
● 2026-08-03 06:36:38

○A46.30.213.1262026-03-06 → 2026-04-08 · 5 obs

○ 2017-06-21 22:29:18
● 2026-03-06 10:56:52
● 2026-04-08 03:29:20
○ 2026-04-23 03:27:44
○ 2026-08-03 06:36:38

○A50.63.202.502016-01-13 → 2017-06-21 · 4 obs

● 2016-01-13 21:10:10
● 2017-06-21 22:29:18
○ 2026-03-06 10:56:52
○ 2026-08-03 06:36:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net...	-
inalize.com	ns01.one.com, ns02.one.com	4 records

✅ Authoritative Response

Server:195.206.121.10

NS records: ns01.one.com, ns02.one.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 540ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`46.30.213.121`
AAAA	1	`2a02:2350:5:10b:80c8:b32c:67e4:c0ce`
NS	2	`ns02.one.com, ns01.one.com`
MX	4	`mx1.pub.mailpod10-cph3.one.com (pri: 10), mx4.pub.mailpod10-cph3.one.com (pri: 10)...`
SOA	1	`ns01.one.com hostmaster.one.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns01.one.com, ns01.one.com, ns02.one.com...)

Analysis

IP Addresses

inalize.com has two IP addresses: 46.30.213.121 and 2a02:2350:5:10b:80c8:b32c:67e4:c0ce

Two other host names, along with arosenergy.com, climatizeuk.com and premier-e-cig.com, also share IP numbers with inalize.com.

Name Servers

Two name servers handle the delegation for inalize.com: ns01.one.com and ns02.one.com.

inalize.com shares its NS records with other domains, for example ikljusdal.se, greencybertech.com, zundapp.net and two others.

ns01.one.com and ns02.one.com both carry two IP addresses. The A records for ns01.one.com are 195.206.121.10 and 2001:67c:28cc::10; the A records for ns02.one.com are 185.10.11.10 and 2001:67c:3c0::10.

Mail Servers

Mail for inalize.com is handled by four mail servers: mx1.pub.mailpod10-cph3.one.com, mx2.pub.mailpod10-cph3.one.com, mx3.pub.mailpod10-cph3.one.com and mx4.pub.mailpod10-cph3.one.com.

There is at least a partial MX overlap between inalize.com and other domains, including roermand.dk, ibbes.se, veo.vision and two others.

The hosts mx1.pub.mailpod10-cph3.one.com, mx2.pub.mailpod10-cph3.one.com, mx3.pub.mailpod10-cph3.one.com and mx4.pub.mailpod10-cph3.one.com all resolve to exactly one IP address each: 104.37.34.70, 104.37.34.71, 104.37.34.72 and 104.37.34.73 respectively.