🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`image-to-code.dev`

DNSSEC	⚠️ Not signed
NS	`ns1.reg.ru` ⚠️ Not in zone NS records
		A	2a00:f940:9::1:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.11^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
NS	`ns2.reg.ru` ⚠️ Not in zone NS records
		A	2a00:f940:9::1:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.12^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`

`dev`

	DNSSEC	⚠️ Not signed
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

image-to-code.com

image-to-code.dev

Similar names

code-to-image.pages.dev

Previous names

Next names

DNS History

2 records (2 active, 0 former)

●NSns1.reg.ru2026-10-20 → 2026-11-11 · 2 obs

● 2026-10-20 00:00:44
● 2026-11-11 20:46:52

●NSns2.reg.ru2026-10-20 → 2026-11-11 · 2 obs

● 2026-10-20 00:00:44
● 2026-11-11 20:46:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
image-to-code.dev	ns1.reg.ru, ns2.reg.ru	-

✅ Authoritative Response

Server:176.99.13.12

NS records: ns1.reg.ru, ns2.reg.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for image-to-code.dev (unsigned zone)

⏱️ Timing

Total: 1030ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

image-to-code.dev uses two name servers for its delegation: ns1.reg.ru and ns2.reg.ru.

image-to-code.dev uses the same name servers as several other domains — among them remont-kolodtsa.ru, vznanie.ru, livefond.ru and two more.

Hostnames that resolve to 10 IP addresses:

Hostname ns1.reg.ru directs to 176.99.13.11, 176.99.13.13 and 176.99.13.15 along with 7 other IP addresses.

Hostname ns2.reg.ru directs to 176.99.13.12, 176.99.13.14 and 176.99.13.16 along with 7 other IP addresses.

image-to-code.dev - robtex.com

image-to-code.dev

dev