🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`codedangerously.com`

DNSSEC	⚠️ Not signed
A	3.131.150.69^{🇺🇸 Amazon3.131.0.0/16 EC2 CMH prefix}
		PTR	`ec2-3-131-150-69.us-east-2.compute.amazonaws.com`
NS	`ns1.dnsimple.com` ⭐
		A	2620:111:8004::53^{🇺🇸 AS327712620:111:8004::/48 DNSimple Corporation}
		A	199.247.152.53^{🇺🇸 AS32771199.247.152.0/24 DNSimple Corporation}
NS	`ns2.dnsimple.com`
		A	2620:111:8005::53^{🇺🇸 AS327712620:111:8005::/48 Vultr Customer Route}
		A	199.247.153.53^{🇺🇸 AS32771199.247.153.0/24 Vultr Customer Route}
NS	`ns3.dnsimple.com`
		A	2620:111:8006::53^{🇺🇸 AS327712620:111:8006::/48 DNSimple Corporation}
		A	199.247.154.53^{🇺🇸 AS32771199.247.154.0/24 DNSimple Corporation}
NS	`ns4.dnsimple-edge.org` ⚠️ Not in parent delegation
		A	2620:111:8007::53^{🇺🇸 AS327712620:111:8007::/48 Vultr Customer Route}
		A	199.247.155.53^{🇺🇸 AS32771199.247.155.0/24 Vultr Customer Route}
NS	`ns4.dnsimple.com` ⚠️ Not in zone NS records
		A	2620:111:8007::53^{🇺🇸 AS327712620:111:8007::/48 Vultr Customer Route}
		A	199.247.155.53^{🇺🇸 AS32771199.247.155.0/24 Vultr Customer Route}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	172.253.139.27^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f27.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::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.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::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.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=Tn3NwMaFYtoLIfFlsxFRDH9VBQiHXiy1RSe-IHE6kUc`
SOA	`ns1.dnsimple.com`admin@dnsimple.com serial=1672880829

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

Same first word

codedangerously.com

Previous names

Next names

DNS History

20 records (11 active, 9 former)

●NSns1.dnsimple.com2026-08-20 → 2026-08-25 · 3 obs

○ 2019-05-02 04:44:54
● 2026-08-20 10:19:40
● 2026-08-25 10:43:14

●NSns2.dnsimple.com2026-08-20 → 2026-08-25 · 3 obs

○ 2019-05-02 04:44:54
● 2026-08-20 10:19:40
● 2026-08-25 10:43:14

●NSns3.dnsimple.com2026-08-20 → 2026-08-25 · 3 obs

○ 2019-05-02 04:44:54
● 2026-08-20 10:19:40
● 2026-08-25 10:43:14

●NSns4.dnsimple-edge.org2026-08-20 → 2026-08-25 · 3 obs

○ 2019-05-02 04:44:54
● 2026-08-20 10:19:40
● 2026-08-25 10:43:14

●NSns4.dnsimple.com2026-08-20 → 2026-08-25 · 3 obs

○ 2019-05-02 04:44:54
● 2026-08-20 10:19:40
● 2026-08-25 10:43:14

○NSvern.ns.cloudflare.com2017-03-16 → 2019-05-02 · 4 obs

● 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

○NSzara.ns.cloudflare.com2017-03-16 → 2019-05-02 · 4 obs

● 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

●MXalt1.aspmx.l.google.com2017-03-16 → 2026-08-25 · 2 obs

● 2017-03-16 18:02:32
● 2026-08-25 10:43:14

●MXalt2.aspmx.l.google.com2017-03-16 → 2026-08-25 · 2 obs

● 2017-03-16 18:02:32
● 2026-08-25 10:43:14

●MXalt3.aspmx.l.google.com2017-03-16 → 2026-08-25 · 2 obs

● 2017-03-16 18:02:32
● 2026-08-25 10:43:14

●MXalt4.aspmx.l.google.com2017-03-16 → 2026-08-25 · 2 obs

● 2017-03-16 18:02:32
● 2026-08-25 10:43:14

●MXaspmx.l.google.com2017-03-16 → 2026-08-25 · 2 obs

● 2017-03-16 18:02:32
● 2026-08-25 10:43:14

○MXjohmiqejgsqf5xsw435bp6rxqsgmw45334mgy65ygu3l2osqm7oq.mx-verification.google.com2017-03-16 → 2019-05-02 · 4 obs

● 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

○A104.18.58.1892017-03-16 → 2019-05-02 · 4 obs

● 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

○A104.18.59.1892017-03-16 → 2019-05-02 · 4 obs

● 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

○A2400:cb00:2048:1::6812:3abd2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:02:32
○ 2019-05-02 04:44:54
○ 2026-08-25 10:43:14

○A2400:cb00:2048:1::6812:3bbd2017-03-16 → 2017-03-16 · 3 obs

● 2017-03-16 18:02:32
○ 2019-05-02 04:44:54
○ 2026-08-25 10:43:14

○A2606:4700:30::6812:3abd2019-05-02 → 2019-05-02 · 4 obs

○ 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

○A2606:4700:30::6812:3bbd2019-05-02 → 2019-05-02 · 4 obs

○ 2017-03-16 18:02:32
● 2019-05-02 04:44:54
○ 2026-08-20 10:19:40
○ 2026-08-25 10:43:14

●A3.131.150.692026-08-20 → 2026-08-25 · 3 obs

○ 2019-05-02 04:44:54
● 2026-08-20 10:19:40
● 2026-08-25 10:43:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
codedangerously.com	ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com, ns4.dnsimple.com	8 records

✅ Authoritative Response

Server:199.247.155.53

NS records: ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com, ns4.dnsimple.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for codedangerously.com (unsigned zone)

⏱️ Timing

Total: 331ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.131.150.69`
NS	4	`ns1.dnsimple.com, ns2.dnsimple.com...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`google-site-verification=Tn3NwMaFYtoLIfF`
SOA	1	`ns1.dnsimple.com admin.dnsimple.com`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.dnsimple.com, ns1.dnsimple.com, ns2.dnsimple.com...)

Analysis

IP Addresses

codedangerously.com resolves to just one IP address, 3.131.150.69.

Two other host names, along with f5.assetsplan.net, successcreeations.net and enderpollack.com, also share IP numbers with codedangerously.com.

Name Servers

codedangerously.com delegates to five name servers: ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com and two others.

codedangerously.com shares at least some of its name servers with other domains, including taxfreewealthwebinar.com, maichimp.net, paliatsos.com and two others.

The name servers ns4.dnsimple.com, ns4.dnsimple-edge.org, ns2.dnsimple-edge.net and two others are commonly seen in use alongside these name servers.

Host names that have two IP addresses:

ns1.dnsimple.com directs traffic to 199.247.152.53 and 2620:111:8004::53.

ns2.dnsimple.com directs traffic to 199.247.153.53 and 2620:111:8005::53.

ns3.dnsimple.com directs traffic to 199.247.154.53 and 2620:111:8006::53.

ns4.dnsimple.com directs traffic to 199.247.155.53 and 2620:111:8007::53.

ns4.dnsimple-edge.org directs traffic to 199.247.155.53 and 2620:111:8007::53.

Both ns4.dnsimple.com and ns4.dnsimple-edge.org resolve to 2620:111:8007::53 IP addresses each.

Both ns4.dnsimple.com and ns4.dnsimple-edge.org resolve to 199.247.155.53 IP addresses each.

Mail Servers

Mail for codedangerously.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.

There is at least a partial MX overlap between codedangerously.com and other domains, including flashfitness.in, acorntrainsystems.com, ristorantepionono.it 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.27 and 2607:f8b0:4004:c1b::1b.

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

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

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

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