🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`technicallyresolution.com`

DNSSEC	⚠️ Not signed
A	23.111.84.4^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	23.111.84.220^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	23.111.84.228^{🇳🇱 SERVERS23.111.84.0/24 .COM NL01 SPECIFIC}
A	172.240.108.68^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.108.76^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.108.84^{🇺🇸 SERVERS172.240.108.0/24 .COM US WAS1}
A	172.240.127.234^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.242^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.243^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.127.244^{🇺🇸 SERVERS172.240.127.0/24 .COM WAS1}
A	172.240.253.132^{🇺🇸 SERVERS172.240.253.0/24 .COM WAS1}
A	172.255.141.4^{🇳🇱 SERVERS172.255.141.0/24 .COM AMS3}
NS	`ns1.publicdnsservice.com` ⭐
		A	52.223.51.231^{🇺🇸 Amazon52.223.48.0/20}
			PTR	`aa378b12f9b002b84.awsglobalaccelerator.com`
NS	`ns2.publicdnsservice.com`
		A	99.83.185.193^{🇺🇸 Amazon99.83.176.0/20}
			PTR	`aa378b12f9b002b84.awsglobalaccelerator.com`
SOA	`ns1.publicdnsservice.com`hostmaster@technicallyresolution.com 2026-10-21 #4

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

⚠️ On DNS blocklist: tif

Same first word

technicallyresolution.com

Previous names

Next names

DNS History

16 records (14 active, 2 former)

●NSns1.publicdnsservice.com2026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●NSns2.publicdnsservice.com2026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.108.682026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.108.762026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.108.842026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.127.2342026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.127.2422026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.127.2432026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.127.2442026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.240.253.1322026-04-11 → 2026-10-28 · 2 obs

● 2026-04-11 19:22:30
● 2026-10-28 20:57:12

●A172.255.141.42026-08-09 → 2026-10-28 · 5 obs

○ 2026-04-11 19:22:30
● 2026-08-09 01:54:38
○ 2026-10-28 03:17:16
● 2026-10-28 11:40:48
● 2026-10-28 20:57:12

○A23.111.84.1162026-08-09 → 2026-08-09 · 4 obs

○ 2026-04-11 19:22:30
● 2026-08-09 01:54:38
○ 2026-09-04 03:34:20
○ 2026-10-28 20:57:12

○A23.111.84.1242026-08-09 → 2026-08-09 · 4 obs

○ 2026-04-11 19:22:30
● 2026-08-09 01:54:38
○ 2026-09-04 03:34:20
○ 2026-10-28 20:57:12

●A23.111.84.2202026-08-09 → 2026-10-28 · 5 obs

○ 2026-04-11 19:22:30
● 2026-08-09 01:54:38
○ 2026-09-20 19:18:28
● 2026-10-17 06:54:30
● 2026-10-28 20:57:12

●A23.111.84.2282026-08-09 → 2026-10-28 · 5 obs

○ 2026-04-11 19:22:30
● 2026-08-09 01:54:38
○ 2026-09-20 19:18:28
● 2026-10-17 06:54:30
● 2026-10-28 20:57:12

●A23.111.84.42026-08-09 → 2026-10-28 · 5 obs

○ 2026-04-11 19:22:30
● 2026-08-09 01:54:38
○ 2026-09-20 19:18:28
● 2026-10-17 06:54:30
● 2026-10-28 20:57:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
technicallyresolution.com	ns1.publicdnsservice.com, ns2.publicdnsservice.com	2 records

✅ Authoritative Response

Server:99.83.185.193

NS records: ns1.publicdnsservice.com, ns2.publicdnsservice.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for technicallyresolution.com (unsigned zone)

⏱️ Timing

Total: 965ms | Queries: -

📄 Records

Type	Count	Sample Data
A	12	`172.240.108.68, 172.240.253.132...`
NS	2	`ns1.publicdnsservice.com, ns2.publicdnsservice.com`
SOA	1	`ns1.publicdnsservice.com hostmaster.tech`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.publicdnsservice.com, ns2.publicdnsservice.com)

Analysis

IP Addresses

technicallyresolution.com points to 12 IP addresses, including 23.111.84.4, 23.111.84.220 and 23.111.84.228, plus 9 other.

concerntyreaimless.com, literallyflickercomplaints.com, exceedinglytemperaturedeclared.com plus two other host names have IP numbers in common with technicallyresolution.com.

Name Servers

technicallyresolution.com has two authoritative name servers — ns1.publicdnsservice.com and ns2.publicdnsservice.com.

The name server configuration of technicallyresolution.com is shared with other domains, for instance distractingzodiacperpetrate.com, anticipationcandiddeserted.com, factorynobody.com and two others.

The name servers for technicallyresolution.com overlap at least partially with those of other domains — for example grindedtate.com.

ns1.publicdnsservice.com and ns2.publicdnsservice.com each resolve to one IP number: ns1.publicdnsservice.com points to 52.223.51.231 and ns2.publicdnsservice.com points to 99.83.185.193.

technicallyresolution.com - robtex.com