coderouge.ca - dns.ninja

`coderouge.ca`

DNSSEC	⚠️ Not signed
A	64.98.135.49^{🇺🇸 TUCOWS-364.98.135.0/24 Tucows.com Co.}
NS	`dns1.name-services.com` ⭐
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns1.name-services.com`
NS	`dns2.name-services.com`
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns2.name-services.com`
NS	`dns3.name-services.com`
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns3.name-services.com`
NS	`dns4.name-services.com`
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns4.name-services.com`
NS	`dns5.name-services.com`
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns5.name-services.com`
TXT	`v=spf1 -all`
SOA	`dns1.name-services.com`info@name-services.com serial=1637758419

`ca`

	DNSSEC	🔒 Signed (DS record present)
	NS	`prd-czp-05.corp.cira.ca` ⭐
	NS	`any.ca-servers.ca`
	NS	`c.ca-servers.ca`
	NS	`d.ca-servers.ca`
	NS	`j.ca-servers.ca`
	SOA	`prd-czp-05.corp.cira.ca`admin-dns@cira.ca serial=2608031900

WOT: SAFE (61/100)

Same first word

coderouge.ca

coderouge.com

coderouge.org

Similar names

coderogue.net

coderogue.com

roguecode.co.za

coderogue.org

ergoeduco.com

rougecode.com

decorouge.com

DNS History

16 records (6 active, 10 former)

○NSdns1.datacentres.rogers.com2016-07-06 → 2017-03-30 · 5 obs

○ 2016-03-07 19:47:08
● 2016-07-06 06:04:02
● 2017-03-30 20:12:16
○ 2020-04-10 16:05:24
○ 2026-08-03 19:54:00

●NSdns1.name-services.com2026-04-07 → 2026-08-03 · 3 obs

○ 2020-04-10 16:05:24
● 2026-04-07 20:37:06
● 2026-08-03 19:54:00

○NSdns2.datacentres.rogers.com2016-07-06 → 2017-03-30 · 5 obs

○ 2016-03-07 19:47:08
● 2016-07-06 06:04:02
● 2017-03-30 20:12:16
○ 2020-04-10 16:05:24
○ 2026-08-03 19:54:00

●NSdns2.name-services.com2026-04-07 → 2026-08-03 · 3 obs

○ 2020-04-10 16:05:24
● 2026-04-07 20:37:06
● 2026-08-03 19:54:00

○NSdns3.datacentres.rogers.com2016-07-06 → 2017-03-30 · 5 obs

○ 2016-03-07 19:47:08
● 2016-07-06 06:04:02
● 2017-03-30 20:12:16
○ 2020-04-10 16:05:24
○ 2026-08-03 19:54:00

●NSdns3.name-services.com2026-04-07 → 2026-08-03 · 3 obs

○ 2020-04-10 16:05:24
● 2026-04-07 20:37:06
● 2026-08-03 19:54:00

●NSdns4.name-services.com2026-04-07 → 2026-08-03 · 3 obs

○ 2020-04-10 16:05:24
● 2026-04-07 20:37:06
● 2026-08-03 19:54:00

●NSdns5.name-services.com2026-04-07 → 2026-08-03 · 3 obs

○ 2020-04-10 16:05:24
● 2026-04-07 20:37:06
● 2026-08-03 19:54:00

○NSns1.mdnsservice.com2020-04-10 → 2020-04-10 · 4 obs

○ 2017-03-30 20:12:16
● 2020-04-10 16:05:24
○ 2026-04-07 20:37:06
○ 2026-08-03 19:54:00

○NSns10.primus.ca2015-08-13 → 2016-03-07 · 4 obs

● 2015-08-13 19:22:36
● 2016-03-07 19:47:08
○ 2016-07-06 06:04:02
○ 2026-08-03 19:54:00

○NSns11.primus.ca2015-08-13 → 2016-03-07 · 4 obs

● 2015-08-13 19:22:36
● 2016-03-07 19:47:08
○ 2016-07-06 06:04:02
○ 2026-08-03 19:54:00

○NSns12.primus.ca2015-08-13 → 2016-03-07 · 4 obs

● 2015-08-13 19:22:36
● 2016-03-07 19:47:08
○ 2016-07-06 06:04:02
○ 2026-08-03 19:54:00

○NSns2.mdnsservice.com2020-04-10 → 2020-04-10 · 4 obs

○ 2017-03-30 20:12:16
● 2020-04-10 16:05:24
○ 2026-04-07 20:37:06
○ 2026-08-03 19:54:00

○NSns3.mdnsservice.com2020-04-10 → 2020-04-10 · 4 obs

○ 2017-03-30 20:12:16
● 2020-04-10 16:05:24
○ 2026-04-07 20:37:06
○ 2026-08-03 19:54:00

○A216.40.47.172020-04-10 → 2020-04-10 · 3 obs

● 2020-04-10 16:05:24
○ 2026-04-07 20:37:06
○ 2026-08-03 19:54:00

●A64.98.135.492026-04-07 → 2026-08-03 · 3 obs

○ 2020-04-10 16:05:24
● 2026-04-07 20:37:06
● 2026-08-03 19:54:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ca	d.ca-servers.ca, j.ca-servers.ca, any.ca-servers.ca, c.ca-servers.ca	-
coderouge.ca	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	-

✅ Authoritative Response

Server:216.40.47.201

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for coderouge.ca (unsigned zone)

⏱️ Timing

Total: 841ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.98.135.49`
NS	5	`dns1.name-services.com, dns3.name-services.com...`
TXT	1	`v=spf1 -all`
SOA	1	`dns1.name-services.com info.name-service`

Analysis

IP Addresses

coderouge.ca has exactly one IP address — 64.98.135.49.

nepaladventures.com, canyouseemenow.com, derbycitymagic.com plus two other host names have IP numbers in common with coderouge.ca.

Name Servers

Five name servers handle delegation for coderouge.ca: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.

coderouge.ca has at least partial name server overlap with other domains, such as breadcorner.net, recommendedautorepair.com, eonon.com.tw and two others.

It is common to see these name servers used together with name servers dns4.name-services.com and dns5.name-services.com.

Host names pointing to two IP addresses:

dns1.name-services.com directs traffic to 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.

dns2.name-services.com directs traffic to 216.40.47.201 and 2604:4000:0:d:216:40:47:201.

dns3.name-services.com directs traffic to 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.

dns4.name-services.com directs traffic to 216.40.47.202 and 2604:4000:0:d:216:40:47:202.

dns5.name-services.com directs traffic to 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.