`fersatechnologies.com`

DNSSEC	⚠️ Not signed
A	18.188.179.180^{🇺🇸 Amazon18.188.0.0/16 EC2 CMH prefix}
		PTR	`ec2-18-188-179-180.us-east-2.compute.amazonaws.com`
NS	`ns1.liquidweb.com` ⭐ ⚠️ Not in zone NS records
		A	2607:fad0:0:8927::a^{🇺🇸 LiquidWeb2607:fad0::/48 Vultr Customer Route}
		A	69.16.223.254^{🇺🇸 LiquidWeb69.16.222.0/23 Liquidweb Inc}
			PTR	`ns1.liquidweb.com`
NS	`ns.liquidweb.com` ⚠️ Not in zone NS records
		A	2607:fad0:0:8917::a^{🇺🇸 LiquidWeb2607:fad0::/48 Vultr Customer Route}
		A	69.16.222.254^{🇺🇸 LiquidWeb69.16.222.0/23 Liquidweb Inc}
			PTR	`ns.liquidweb.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	172.253.122.26^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4003:c4a::1a^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f26.1e100.net`
		A	142.251.96.27^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f27.1e100.net`
TXT	`google-site-verification=v2dbE4-wSU_2q7Hq-b-wkE07T6D-__bI84VH91Ka5zo`
TXT	`google-site-verification=vW1gWB_ak8t95LxJyIZsRYXU93bhi-JabpgkqWtEAMg`
SOA	`ns.liquidweb.com`admin@liquidweb.com 2026-03-29 #3

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

Subdomains

netec.fersatechnologies.com

Same first word

fersatechnologies.com

Similar names

safertechnologies.com

fresatechnologies.com

resaftechnologies.com

DNS History

17 records (8 active, 9 former)

●NSns.liquidweb.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

●NSns1.liquidweb.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

○NSns1.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

○NSns2.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

○NSns3.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

○NSns4.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

●MXalt1.aspmx.l.google.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

●MXalt2.aspmx.l.google.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

●MXalt3.aspmx.l.google.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

●MXalt4.aspmx.l.google.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

●MXaspmx.l.google.com2026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

○MXmx7.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

○MXmx8.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

○MXmx9.webfaction.com2018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

●A18.188.179.1802026-02-16 → 2026-03-30 · 3 obs

○ 2018-05-23 02:39:36
● 2026-02-16 07:01:58
● 2026-03-30 06:50:22

○A207.38.86.1532018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

○A2605:de00:1:1:4a:1f:0:302018-05-23 → 2018-05-23 · 3 obs

● 2018-05-23 02:39:36
○ 2026-02-16 07:01:58
○ 2026-03-30 06:50:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
fersatechnologies.com	ns.liquidweb.com, ns1.liquidweb.com	2 records

✅ Authoritative Response

Server:69.16.223.254

NS records: ns.liquidweb.com, ns1.liquidweb.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fersatechnologies.com (unsigned zone)

⏱️ Timing

Total: 192ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`18.188.179.180`
MX	5	`ALT3.ASPMX.L.GOOGLE.com (pri: 10), ALT1.ASPMX.L.GOOGLE.com (pri: 5)...`
TXT	2	`google-site-verification=vW1gWB_ak8t95Lx, google-site-verification=v2dbE4-wSU_2q7H`
SOA	1	`ns.liquidweb.com admin.liquidweb.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns.liquidweb.com, ns1.liquidweb.com)

Analysis

Hierarchy

The parent of netec.fersatechnologies.com is fersatechnologies.com.

IP Addresses

fersatechnologies.com points to a single IP: 18.188.179.180.

Name Servers

Two name servers ns1.liquidweb.com and ns.liquidweb.com handle delegation for fersatechnologies.com.

fersatechnologies.com uses the same name server setup as other domains, for example vallioniemi.com, personalprotectiontrainingcourses.com, communityprofessor.com, kasnazan.com and 12fret.com.

fersatechnologies.com partially shares name servers with other domains; examples include reliance.nyc, itreader.com, 238.52.72.in-addr.arpa, brandreviews.info and imcp.mx.