technicallywrong.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`technicallywrong.com`

DNSSEC	⚠️ Not signed
A	188.214.128.77^{🇱🇹 CHERRYSERVERS1-AS188.214.128.0/21 CHERRY SERVERS}
		PTR	`vps2.customhost.com`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
MX	`2.rack-host.net` ⭐
		A	208.66.194.178^{🇺🇸 BIZNESSHOSTING208.66.194.0/23 Biznesshosting, Inc. DBA VOLICO 500 Green Rd. Deerfield, FL 33064 US}
SOA	`ns1.dyna-ns.net`hostmaster@technicallywrong.com 2026-10-30 #1

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

Same first word

technicallywrong.com

Previous names

Next names

DNS History

8 records (4 active, 4 former)

●NSns1.dyna-ns.net2026-10-03 → 2026-11-04 · 3 obs

○ 2020-01-22 02:48:22
● 2026-10-03 20:09:46
● 2026-11-04 09:32:46

○NSns1.dynadot.com2015-07-07 → 2020-01-22 · 5 obs

○ 2008-03-13 20:07:02
● 2015-07-07 06:40:48
● 2020-01-22 02:48:22
○ 2026-10-03 20:09:46
○ 2026-11-04 09:32:46

●NSns2.dyna-ns.net2026-10-03 → 2026-11-04 · 3 obs

○ 2020-01-22 02:48:22
● 2026-10-03 20:09:46
● 2026-11-04 09:32:46

○NSns2.dynadot.com2015-07-07 → 2020-01-22 · 5 obs

○ 2008-03-13 20:07:02
● 2015-07-07 06:40:48
● 2020-01-22 02:48:22
○ 2026-10-03 20:09:46
○ 2026-11-04 09:32:46

●MX2.rack-host.net2020-01-22 → 2026-11-04 · 3 obs

○ 2017-02-01 16:12:58
● 2020-01-22 02:48:22
● 2026-11-04 09:32:46

○MXrack-host.net2015-07-07 → 2017-02-01 · 5 obs

○ 2008-03-13 20:07:02
● 2015-07-07 06:40:48
● 2017-02-01 16:12:58
○ 2020-01-22 02:48:22
○ 2026-11-04 09:32:46

●A188.214.128.772020-01-22 → 2026-11-04 · 3 obs

○ 2017-02-01 16:12:58
● 2020-01-22 02:48:22
● 2026-11-04 09:32:46

○A64.85.171.162015-07-07 → 2017-02-01 · 5 obs

○ 2008-03-13 20:07:02
● 2015-07-07 06:40:48
● 2017-02-01 16:12:58
○ 2020-01-22 02:48:22
○ 2026-11-04 09:32:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
technicallywrong.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.24.5

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for technicallywrong.com (unsigned zone)

⏱️ Timing

Total: 1146ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`188.214.128.77`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
MX	1	`2.rack-host.net (pri: 0)`
SOA	1	`ns1.dyna-ns.net hostmaster.technicallywr`

Analysis

IP Addresses

technicallywrong.com resolves to one IP address: 188.214.128.77.

wonderwine.com, employerpolicy.net, www.dmv-ca.com and two other host names share IP numbers with technicallywrong.com.

Name Servers

technicallywrong.com is served by two delegated name servers, ns1.dyna-ns.net and ns2.dyna-ns.net.

technicallywrong.com uses the same name servers as several other domains — among them theweddingsavvy.beauty, orbexy.com, backinup.com and two more.

The DNS delegation for technicallywrong.com at least partly coincides with that of other domains, zugriffskontrolle.de being one example.

Both ns1.dyna-ns.net and ns2.dyna-ns.net resolve to four IP addresses: ns1.dyna-ns.net directs to 162.159.26.92, 162.159.27.158, 2400:cb00:2049:1::a29f:1a5c and 2400:cb00:2049:1::a29f:1b9e, and ns2.dyna-ns.net directs to 162.159.24.5, 162.159.25.5, 2400:cb00:2049:1::a29f:1805 and 2400:cb00:2049:1::a29f:1905.

Mail Servers

Mail for technicallywrong.com is handled by a single mail server, 2.rack-host.net.

technicallywrong.com uses an identical mail server configuration to several other domains — among them southafrika.com, syndigator.com, fasterdomain.com and two more.

There is one IP number for 2.rack-host.net: 208.66.194.178.