codingevent.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`codingevent.com`

DNSSEC	⚠️ Not signed
A	116.203.0.254^{🇩🇪 Hetzner116.203.0.0/16 HETZNER-DC}
		PTR	`webmail.codingevent.com`
NS	`pdns03.domaincontrol.com` ⭐
		A	2603:5:21f0::33^{🇺🇸 GODADDY-DNS2603:5:21f0::/44}
			PTR	`pdns03.domaincontrol.com`
		A	97.74.111.51^{🇺🇸 GODADDY-DNS97.74.110.0/23}
			PTR	`pdns03.domaincontrol.com`
NS	`pdns04.domaincontrol.com`
		A	2603:5:22f0::33^{🇺🇸 GODADDY-DNS2603:5:22f0::/44}
			PTR	`pdns04.domaincontrol.com`
		A	173.201.79.51^{🇺🇸 GODADDY-DNS173.201.78.0/23}
			PTR	`pdns04.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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.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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=LLn9lGfiWAUlbZLg0JuZw3nOFw2kRAsYpFv_Id2b528`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`google-site-verification=kYEZEE15sCRVmcy5eqIDLJ6Zs7rOdvIZZy7vH8s4IVo`
SOA	`pdns03.domaincontrol.com`dns@jomax.net 2025-09-13 #5

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

Subdomains

webmail.codingevent.com

cloud.codingevent.com

Same first word

codingevent.com

Previous names

Next names

DNS History

17 records (8 active, 9 former)

○NSns1.digitalocean.com2018-01-12 → 2018-01-12 · 4 obs

○ 2016-02-07 05:19:14
● 2018-01-12 19:43:58
○ 2026-02-19 13:21:28
○ 2026-08-19 13:41:22

○NSns2.digitalocean.com2018-01-12 → 2018-01-12 · 4 obs

○ 2016-02-07 05:19:14
● 2018-01-12 19:43:58
○ 2026-02-19 13:21:28
○ 2026-08-19 13:41:22

○NSns3.digitalocean.com2018-01-12 → 2018-01-12 · 4 obs

○ 2016-02-07 05:19:14
● 2018-01-12 19:43:58
○ 2026-02-19 13:21:28
○ 2026-08-19 13:41:22

○NSns77.domaincontrol.com2015-06-22 → 2015-11-16 · 4 obs

● 2015-06-22 02:04:24
● 2015-11-16 23:49:42
○ 2016-02-07 05:19:14
○ 2026-08-19 13:41:22

○NSns78.domaincontrol.com2015-06-22 → 2015-11-16 · 4 obs

● 2015-06-22 02:04:24
● 2015-11-16 23:49:42
○ 2016-02-07 05:19:14
○ 2026-08-19 13:41:22

●NSpdns03.domaincontrol.com2026-02-19 → 2026-08-19 · 3 obs

○ 2018-01-12 19:43:58
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

●NSpdns04.domaincontrol.com2026-02-19 → 2026-08-19 · 3 obs

○ 2018-01-12 19:43:58
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

●MXalt1.aspmx.l.google.com2026-02-19 → 2026-08-19 · 3 obs

○ 2016-02-07 05:19:14
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

●MXalt2.aspmx.l.google.com2026-02-19 → 2026-08-19 · 3 obs

○ 2016-02-07 05:19:14
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

●MXalt3.aspmx.l.google.com2026-02-19 → 2026-08-19 · 3 obs

○ 2016-02-07 05:19:14
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

●MXalt4.aspmx.l.google.com2026-02-19 → 2026-08-19 · 3 obs

○ 2016-02-07 05:19:14
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

●MXaspmx.l.google.com2026-02-19 → 2026-08-19 · 3 obs

○ 2016-02-07 05:19:14
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

○MXmailstore1.secureserver.net2015-06-22 → 2015-11-16 · 4 obs

● 2015-06-22 02:04:24
● 2015-11-16 23:49:42
○ 2016-02-07 05:19:14
○ 2026-08-19 13:41:22

○MXsmtp.secureserver.net2015-06-22 → 2015-11-16 · 4 obs

● 2015-06-22 02:04:24
● 2015-11-16 23:49:42
○ 2016-02-07 05:19:14
○ 2026-08-19 13:41:22

●A116.203.0.2542026-02-19 → 2026-08-19 · 3 obs

○ 2018-01-12 19:43:58
● 2026-02-19 13:21:28
● 2026-08-19 13:41:22

○A159.89.23.552018-01-12 → 2018-01-12 · 4 obs

○ 2016-02-07 05:19:14
● 2018-01-12 19:43:58
○ 2026-02-19 13:21:28
○ 2026-08-19 13:41:22

○A50.63.202.522015-06-22 → 2015-11-16 · 4 obs

● 2015-06-22 02:04:24
● 2015-11-16 23:49:42
○ 2016-02-07 05:19:14
○ 2026-08-19 13:41:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
codingevent.com	pdns03.domaincontrol.com, pdns04.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.79.51

NS records: pdns03.domaincontrol.com, pdns04.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for codingevent.com (unsigned zone)

⏱️ Timing

Total: 191ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`116.203.0.254`
NS	2	`pdns03.domaincontrol.com, pdns04.domaincontrol.com`
MX	5	`alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...`
TXT	3	`google-site-verification=LLn9lGfiWAUlbZL, v=spf1 include:_spf.google.com ~all...`
SOA	1	`pdns03.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (pdns03.domaincontrol.com, pdns03.domaincontrol.com, pdns04.domaincontrol.com...)

Analysis

Hierarchy

webmail.codingevent.com and cloud.codingevent.com are both subdomains of codingevent.com.

IP Addresses

codingevent.com resolves to one IP address: 116.203.0.254.

zmgm.org.tr, mail.zmgm.org.tr, webmail.codingevent.com and cloud.codingevent.com are among the host names that share IP numbers with codingevent.com.

Name Servers

codingevent.com has two authoritative name servers — pdns03.domaincontrol.com and pdns04.domaincontrol.com.

codingevent.com uses the same name servers as several other domains — among them bourgeoisford.com, d3photo.com, sapsafety.com and two more.

codingevent.com shares at least some of its name servers with other domains, for example demw.com, honoree-music.com, ereferral.ca and activeserveng.com.

Both pdns03.domaincontrol.com and pdns04.domaincontrol.com have two IP addresses each. pdns03.domaincontrol.com resolves to 97.74.111.51 and 2603:5:21f0::33; pdns04.domaincontrol.com resolves to 173.201.79.51 and 2603:5:22f0::33.

Mail Servers

codingevent.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

codingevent.com has at least partial mail server overlap with other domains such as mecoxgardens.com, elmika.co.id, nzcc.org and two more.

The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com resolves to 192.178.155.26 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b.

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

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

alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.