fsloader.com - dns.ninja

`fsloader.com`

DNSSEC	⚠️ Not signed
A	104.224.230.219^{🇺🇸 ESITED-1104.224.192.0/18 WHDOT CUSTOMER NET1}
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`
SOA	`dns1.name-services.com`info@name-services.com serial=1560735007

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

Same first word

fsloader.com

Similar names

DNS History

15 records (6 active, 9 former)

●NSdns1.name-services.com2026-02-14 → 2026-08-03 · 3 obs

○ 2018-06-14 05:45:10
● 2026-02-14 22:01:10
● 2026-08-03 01:03:00

○NSdns1.supremedns.com2015-07-20 → 2015-07-20 · 4 obs

○ 2008-11-08 15:55:28
● 2015-07-20 16:27:44
○ 2015-12-08 09:16:28
○ 2026-08-03 01:03:00

●NSdns2.name-services.com2026-02-14 → 2026-08-03 · 3 obs

○ 2018-06-14 05:45:10
● 2026-02-14 22:01:10
● 2026-08-03 01:03:00

○NSdns2.supremedns.com2015-07-20 → 2015-07-20 · 4 obs

○ 2008-11-08 15:55:28
● 2015-07-20 16:27:44
○ 2015-12-08 09:16:28
○ 2026-08-03 01:03:00

●NSdns3.name-services.com2026-02-14 → 2026-08-03 · 3 obs

○ 2018-06-14 05:45:10
● 2026-02-14 22:01:10
● 2026-08-03 01:03:00

●NSdns4.name-services.com2026-02-14 → 2026-08-03 · 3 obs

○ 2018-06-14 05:45:10
● 2026-02-14 22:01:10
● 2026-08-03 01:03:00

●NSdns5.name-services.com2026-02-14 → 2026-08-03 · 3 obs

○ 2018-06-14 05:45:10
● 2026-02-14 22:01:10
● 2026-08-03 01:03:00

○NSv1s1.xundns.com2016-03-13 → 2016-07-17 · 5 obs

○ 2015-12-08 09:16:28
● 2016-03-13 12:42:46
● 2016-07-17 03:18:38
○ 2018-06-14 05:45:10
○ 2026-08-03 01:03:00

○NSv1s2.xundns.com2016-03-13 → 2016-07-17 · 5 obs

○ 2015-12-08 09:16:28
● 2016-03-13 12:42:46
● 2016-07-17 03:18:38
○ 2018-06-14 05:45:10
○ 2026-08-03 01:03:00

○MXmx.ym.163.com2016-03-13 → 2016-07-17 · 5 obs

○ 2015-12-08 09:16:28
● 2016-03-13 12:42:46
● 2016-07-17 03:18:38
○ 2018-06-14 05:45:10
○ 2026-08-03 01:03:00

○MXmx1.supremebox.com2015-07-20 → 2015-07-20 · 4 obs

○ 2008-11-08 15:55:28
● 2015-07-20 16:27:44
○ 2015-12-08 09:16:28
○ 2026-08-03 01:03:00

○MXmx2.supremebox.com2015-07-20 → 2015-07-20 · 4 obs

○ 2008-11-08 15:55:28
● 2015-07-20 16:27:44
○ 2015-12-08 09:16:28
○ 2026-08-03 01:03:00

●A104.224.230.2192026-02-14 → 2026-08-03 · 3 obs

○ 2018-06-14 05:45:10
● 2026-02-14 22:01:10
● 2026-08-03 01:03:00

○A137.175.20.342016-03-13 → 2016-07-17 · 5 obs

○ 2015-12-08 09:16:28
● 2016-03-13 12:42:46
● 2016-07-17 03:18:38
○ 2018-06-14 05:45:10
○ 2026-08-03 01:03:00

○A198.23.51.2162015-07-20 → 2015-07-20 · 4 obs

○ 2008-11-08 15:55:28
● 2015-07-20 16:27:44
○ 2015-12-08 09:16:28
○ 2026-08-03 01:03:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
fsloader.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server:64.98.148.137

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 fsloader.com (unsigned zone)

⏱️ Timing

Total: 237ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.224.230.219`
NS	5	`dns2.name-services.com, dns5.name-services.com...`
SOA	1	`dns1.name-services.com info.name-service`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

Analysis

IP Addresses

fsloader.com has exactly one IP address — 104.224.230.219.

Name Servers

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

fsloader.com has at least partial name server overlap with other domains, such as bitcoinmicrolending.com, sempai.com, barnessolutions.us 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 has two IP addresses: 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.

dns2.name-services.com has two IP addresses: 216.40.47.201 and 2604:4000:0:d:216:40:47:201.

dns3.name-services.com has two IP addresses: 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.

dns4.name-services.com has two IP addresses: 216.40.47.202 and 2604:4000:0:d:216:40:47:202.

dns5.name-services.com has two IP addresses: 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.