scan1.com - dns.ninja

`scan1.com`

DNSSEC	⚠️ Not signed
NS	`dns101.register.com` ⭐
		A	162.159.24.117^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`dns102.register.com`
		A	162.159.25.158^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`DNS101.REGISTER.com`root@REGISTER.com serial=120042815

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

Same first word

scan1.com

scan1.top

scan1.net

Similar names

nacs1.org

nsca1.com.mx

1scan.net

cans1.com

asn1c.com

1scan.com

1scan.co.uk

1scan.ai

DNS History

13 records (2 active, 11 former)

○NSdns067.b.register.com2015-07-03 → 2016-04-30 · 5 obs

○ 2008-03-05 18:50:08
● 2015-07-03 13:11:24
● 2016-04-30 01:02:14
○ 2026-05-29 09:30:18
○ 2026-08-13 12:07:16

○NSdns1.name-services.com2008-03-05 → 2008-03-05 · 3 obs

● 2008-03-05 18:50:08
○ 2015-07-03 13:11:24
○ 2026-08-13 12:07:16

●NSdns101.register.com2026-05-29 → 2026-08-13 · 3 obs

○ 2016-04-30 01:02:14
● 2026-05-29 09:30:18
● 2026-08-13 12:07:16

●NSdns102.register.com2026-05-29 → 2026-08-13 · 3 obs

○ 2016-04-30 01:02:14
● 2026-05-29 09:30:18
● 2026-08-13 12:07:16

○NSdns189.a.register.com2015-07-03 → 2016-04-30 · 5 obs

○ 2008-03-05 18:50:08
● 2015-07-03 13:11:24
● 2016-04-30 01:02:14
○ 2026-05-29 09:30:18
○ 2026-08-13 12:07:16

○NSdns2.name-services.com2008-03-05 → 2008-03-05 · 3 obs

● 2008-03-05 18:50:08
○ 2015-07-03 13:11:24
○ 2026-08-13 12:07:16

○NSdns208.c.register.com2015-07-03 → 2016-04-30 · 5 obs

○ 2008-03-05 18:50:08
● 2015-07-03 13:11:24
● 2016-04-30 01:02:14
○ 2026-05-29 09:30:18
○ 2026-08-13 12:07:16

○NSdns249.d.register.com2015-07-03 → 2016-04-30 · 5 obs

○ 2008-03-05 18:50:08
● 2015-07-03 13:11:24
● 2016-04-30 01:02:14
○ 2026-05-29 09:30:18
○ 2026-08-13 12:07:16

○NSdns3.name-services.com2008-03-05 → 2008-03-05 · 3 obs

● 2008-03-05 18:50:08
○ 2015-07-03 13:11:24
○ 2026-08-13 12:07:16

○NSdns4.name-services.com2008-03-05 → 2008-03-05 · 3 obs

● 2008-03-05 18:50:08
○ 2015-07-03 13:11:24
○ 2026-08-13 12:07:16

○NSdns5.name-services.com2008-03-05 → 2008-03-05 · 3 obs

● 2008-03-05 18:50:08
○ 2015-07-03 13:11:24
○ 2026-08-13 12:07:16

○MXp.webcom.ctmail.com2016-04-30 → 2016-04-30 · 3 obs

● 2016-04-30 01:02:14
○ 2026-05-29 09:30:18
○ 2026-08-13 12:07:16

○A8.15.231.2262008-03-05 → 2008-03-05 · 3 obs

● 2008-03-05 18:50:08
○ 2015-07-03 13:11:24
○ 2026-08-13 12:07:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
scan1.com	dns101.register.com, dns102.register.com	2 records

✅ Authoritative Response

Server:162.159.24.117

NS records: dns101.register.com, dns102.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for scan1.com (unsigned zone)

⏱️ Timing

Total: 261ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns101.register.com, dns102.register.com`
SOA	1	`DNS101.REGISTER.com root.REGISTER.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

Name Servers

scan1.com has two authoritative name servers — dns101.register.com and dns102.register.com.

scan1.com shares its name server setup with other domains, including chiquirruca.com, cocospanama.com, arpeet.com and two others.

The name servers for scan1.com overlap at least partially with those of other domains — for example tek-is.com.

dns101.register.com resolves to 162.159.24.117. dns102.register.com resolves to 162.159.25.158. Both host names point to a single IP number.