wellfedweb.com - dns.ninja

`wellfedweb.com`

DNSSEC	⚠️ Not signed
A	69.64.147.244^{🇺🇸 Amazon69.64.147.0/24 EC2 Prefix}
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=1495276559

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

Previously MX for

wellfedweb.com

Subdomains

ns2.wellfedweb.com

ns1.wellfedweb.com

Same first word

wellfedweb.com

DNS History

18 records (6 active, 12 former)

●NSdns1.name-services.com2016-01-21 → 2026-06-15 · 3 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2026-06-15 18:39:02

●NSdns2.name-services.com2016-01-21 → 2026-06-15 · 3 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2026-06-15 18:39:02

●NSdns3.name-services.com2016-01-21 → 2026-06-15 · 3 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2026-06-15 18:39:02

●NSdns4.name-services.com2016-01-21 → 2026-06-15 · 3 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2026-06-15 18:39:02

●NSdns5.name-services.com2016-01-21 → 2026-06-15 · 3 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2026-06-15 18:39:02

○NSns1.wellfedweb.com2015-06-09 → 2015-10-25 · 5 obs

○ 2008-03-08 04:27:34
● 2015-06-09 04:48:52
● 2015-10-25 06:11:00
○ 2016-01-21 15:17:54
○ 2026-06-15 18:39:02

○NSns1627.websitewelcome.com2015-06-09 → 2015-10-25 · 5 obs

○ 2008-03-08 04:27:34
● 2015-06-09 04:48:52
● 2015-10-25 06:11:00
○ 2016-01-21 15:17:54
○ 2026-06-15 18:39:02

○NSns2.wellfedweb.com2015-06-09 → 2015-10-25 · 5 obs

○ 2008-03-08 04:27:34
● 2015-06-09 04:48:52
● 2015-10-25 06:11:00
○ 2016-01-21 15:17:54
○ 2026-06-15 18:39:02

○NSns35.domaincontrol.com2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 04:27:34
○ 2015-06-09 04:48:52
○ 2026-06-15 18:39:02

○NSns36.domaincontrol.com2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 04:27:34
○ 2015-06-09 04:48:52
○ 2026-06-15 18:39:02

○MXmailstore1.secureserver.net2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 04:27:34
○ 2015-06-09 04:48:52
○ 2026-06-15 18:39:02

○MXp.nsm.ctmail.com2016-01-21 → 2016-04-17 · 5 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2016-04-17 12:59:26
○ 2016-11-26 23:09:30
○ 2026-06-15 18:39:02

○MXsmtp.secureserver.net2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 04:27:34
○ 2015-06-09 04:48:52
○ 2026-06-15 18:39:02

○MXwellfedweb.com2015-06-09 → 2015-10-25 · 5 obs

○ 2008-03-08 04:27:34
● 2015-06-09 04:48:52
● 2015-10-25 06:11:00
○ 2016-01-21 15:17:54
○ 2026-06-15 18:39:02

○A192.185.138.32015-06-09 → 2015-10-25 · 5 obs

○ 2008-03-08 04:27:34
● 2015-06-09 04:48:52
● 2015-10-25 06:11:00
○ 2016-01-21 15:17:54
○ 2026-06-15 18:39:02

○A68.178.232.1002008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 04:27:34
○ 2015-06-09 04:48:52
○ 2026-06-15 18:39:02

○A69.64.147.2432016-01-21 → 2016-11-26 · 5 obs

○ 2015-10-25 06:11:00
● 2016-01-21 15:17:54
● 2016-11-26 23:09:30
○ 2017-07-06 16:04:52
○ 2026-06-15 18:39:02

●A69.64.147.2442017-07-06 → 2026-06-15 · 3 obs

○ 2016-11-26 23:09:30
● 2017-07-06 16:04:52
● 2026-06-15 18:39:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
wellfedweb.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.139

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

⏱️ Timing

Total: 261ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`69.64.147.244`
NS	5	`dns5.name-services.com, dns2.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

Hierarchy

ns2.wellfedweb.com and ns1.wellfedweb.com are both subdomains of wellfedweb.com.

IP Addresses

wellfedweb.com resolves to one IP address: 69.64.147.244.

galleries.jasmin44.easyjournal.com, megawp.com, sgwww.pollada.com and two other host names share IP numbers with wellfedweb.com.

Name Servers

wellfedweb.com has five name servers, which are dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.

wellfedweb.com has at least partial name server overlap with other domains, such as rideshare.ca, ergoquiz.com, rubberlist.com 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.

Hostnames that resolve 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.