dynamicelements.no - dns.ninja

`dynamicelements.no`

DNSSEC	⚠️ Not signed
A	13.70.37.114^{🇭🇰 Microsoft13.64.0.0/11 MICROSOFT}
NS	`ns81.domaincontrol.com` ⭐
		A	97.74.101.32^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns61.domaincontrol.com`
NS	`ns82.domaincontrol.com`
		A	173.201.69.32^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns62.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	172.253.139.26^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 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::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`apple-domain-verification=ex20h8PiIV9fbQHl`
TXT	`atlassian-domain-verification=WLiIHrH0tz71nProeaiOx7owr2CKFCxZKjRhceDTG88f8H0...`
TXT	`MS=7B48230022E9FE69CAF03CB1B00EEC18B853A2C7`
TXT	`smartsheet-site-validation=WsgdGtvv92F6FPyY33ZVWGKBDAnYA5wg`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`_mqnz9hxu71k88bxhmydkd1t23ldv8oq`
SOA	`ns81.domaincontrol.com`dns@jomax.net 2026-06-09 #2

`no`

	DNSSEC	🔒 Signed (DS record present)
	NS	`charm.norid.no` ⭐
	NS	`i.nic.no`
	NS	`njet.norid.no`
	NS	`not.norid.no`
	NS	`x.nic.no`
	NS	`y.nic.no`
	NS	`z.nic.no`
	SOA	`charm.norid.no`hostmaster@norid.no 2026-07-04 #51

Same first word

dynamicelements.no

dynamicelements.co.za

dynamicelements.info

dynamicelements.com

Similar names

elementdynamics.click

DNS History

15 records (8 active, 7 former)

○NSns01.one.com2015-06-29 → 2018-06-20 · 4 obs

● 2015-06-29 07:33:38
● 2018-06-20 16:20:38
○ 2026-04-05 20:54:56
○ 2026-07-04 16:54:04

○NSns02.one.com2015-06-29 → 2018-06-20 · 4 obs

● 2015-06-29 07:33:38
● 2018-06-20 16:20:38
○ 2026-04-05 20:54:56
○ 2026-07-04 16:54:04

●NSns81.domaincontrol.com2026-04-05 → 2026-07-04 · 3 obs

○ 2018-06-20 16:20:38
● 2026-04-05 20:54:56
● 2026-07-04 16:54:04

●NSns82.domaincontrol.com2026-04-05 → 2026-07-04 · 3 obs

○ 2018-06-20 16:20:38
● 2026-04-05 20:54:56
● 2026-07-04 16:54:04

●MXalt1.aspmx.l.google.com2017-01-08 → 2026-07-04 · 3 obs

○ 2016-04-23 07:50:36
● 2017-01-08 16:30:34
● 2026-07-04 16:54:04

●MXalt2.aspmx.l.google.com2017-01-08 → 2026-07-04 · 3 obs

○ 2016-04-23 07:50:36
● 2017-01-08 16:30:34
● 2026-07-04 16:54:04

●MXalt3.aspmx.l.google.com2017-01-08 → 2026-07-04 · 3 obs

○ 2016-04-23 07:50:36
● 2017-01-08 16:30:34
● 2026-07-04 16:54:04

●MXalt4.aspmx.l.google.com2017-01-08 → 2026-07-04 · 3 obs

○ 2016-04-23 07:50:36
● 2017-01-08 16:30:34
● 2026-07-04 16:54:04

●MXaspmx.l.google.com2017-01-08 → 2026-07-04 · 3 obs

○ 2016-04-23 07:50:36
● 2017-01-08 16:30:34
● 2026-07-04 16:54:04

○MXmxcluster1.one.com2015-06-29 → 2016-04-23 · 4 obs

● 2015-06-29 07:33:38
● 2016-04-23 07:50:36
○ 2017-01-08 16:30:34
○ 2026-07-04 16:54:04

○MXmxcluster2.one.com2015-06-29 → 2016-04-23 · 4 obs

● 2015-06-29 07:33:38
● 2016-04-23 07:50:36
○ 2017-01-08 16:30:34
○ 2026-07-04 16:54:04

●A13.70.37.1142026-04-05 → 2026-07-04 · 3 obs

○ 2018-06-20 16:20:38
● 2026-04-05 20:54:56
● 2026-07-04 16:54:04

○A2a02:2350:5:101:1380:0:39ce:ab552018-06-20 → 2018-06-20 · 4 obs

○ 2017-01-08 16:30:34
● 2018-06-20 16:20:38
○ 2026-04-05 20:54:56
○ 2026-07-04 16:54:04

○A46.30.212.722015-06-29 → 2016-04-23 · 4 obs

● 2015-06-29 07:33:38
● 2016-04-23 07:50:36
○ 2017-01-08 16:30:34
○ 2026-07-04 16:54:04

○A46.30.213.782017-01-08 → 2018-06-20 · 5 obs

○ 2016-04-23 07:50:36
● 2017-01-08 16:30:34
● 2018-06-20 16:20:38
○ 2026-04-05 20:54:56
○ 2026-07-04 16:54:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
no	y.nic.no, njet.norid.no, not.norid.no, x.nic.no...	11 records
dynamicelements.no	ns82.domaincontrol.com, ns81.domaincontrol.com	-

✅ Authoritative Response

Server:97.74.101.32

NS records: ns82.domaincontrol.com, ns81.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dynamicelements.no (unsigned zone)

⏱️ Timing

Total: 1403ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.70.37.114`
NS	2	`ns81.domaincontrol.com, ns82.domaincontrol.com`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	6	`apple-domain-verification=ex20h8PiIV9fbQ, atlassian-domain-verification=WLiIHrH0tz...`
SOA	1	`ns81.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 11

In-bailiwick: 11 (i.nic.no, x.nic.no, y.nic.no...)

Analysis

IP Addresses

dynamicelements.no resolves to just one IP address, 13.70.37.114.

Two other host names, along with zlanze.com, ifis.com.sg and dotts.in, also share IP numbers with dynamicelements.no.

Name Servers

dynamicelements.no uses two name servers for its delegation: ns81.domaincontrol.com and ns82.domaincontrol.com.

dynamicelements.no shares its NS records with other domains, for example bohrkronen-kraatz.de, xquadrat-gmbh.de, kaufhaus-renner.de and two others.

Both ns81.domaincontrol.com and ns82.domaincontrol.com have a single IP address each — ns81.domaincontrol.com resolves to 97.74.101.32 while ns82.domaincontrol.com resolves to 173.201.69.32.

Mail Servers

Five mail servers handle dynamicelements.no: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between dynamicelements.no and other domains, including ns500699.ns500693.ns500693.ns500699.ns500693.ns500588.ns500588.ns500693.ns500699.ns500693.ns500588.ns500602.dtrkdll.com, ns500734.ns500693.ns500693.ns500734.ns500699.ns500699.ns500693.ns500734.ns500699.ns500693.ns500699.ns500693.ns500588.ns500683.ns500699.ns500612.ns500110.dtrkdll.com, apite.io and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 172.253.139.26 and 2607:f8b0:4004:c1d::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.