`routinesolution.com`

DNSSEC	⚠️ Not signed
A	35.220.184.153^{🇭🇰 Google35.220.176.0/20}
		PTR	`153.184.220.35.bc.googleusercontent.com`
NS	`ns1.dnsip.com` ⭐
		A	2001:df2:f080:1::10^{🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	1.193.216.199^{🇨🇳 CHINANET-Henan-Luoyang-IDC1.193.216.0/24 Chinatelecom HeNan Province Network}
		A	218.98.111.202^{🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	218.98.111.206^{🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
NS	`ns2.dnsip.com`
		A	240e:97d:10:1402:0:1:0:1008^{🇨🇳 CHINANET-Guangdong-DongGuan-IDC240e:97d::/36 DongGuan IDC Network}
		A	61.158.128.1^{🇨🇳 CHINA169-Backbone61.158.128.0/17 CNC Group CHINA169 Henan Province Network}
			PTR	`1.128.158.61.ha.cnc`
		A	183.253.57.193^{🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route)}
		A	211.99.99.29^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
		A	211.99.99.33^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
SOA	`ns1.dnsip.com`dnsadmin@dnsip.com serial=1769445129

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

WOT: SAFE (4/100)

Subdomains

hostmaster.routinesolution.com

Same first word

routinesolution.com

DNS History

16 records (3 active, 13 former)

○NSns1.bluehost.com2015-11-09 → 2017-02-15 · 4 obs

● 2015-11-09 02:23:44
● 2017-02-15 04:10:00
○ 2019-03-22 08:40:40
○ 2026-05-13 17:48:18

●NSns1.dnsip.com2026-03-17 → 2026-05-13 · 3 obs

○ 2019-03-22 08:40:40
● 2026-03-17 06:36:30
● 2026-05-13 17:48:18

○NSns1.routinesolution.com2019-03-22 → 2019-03-22 · 4 obs

○ 2017-02-15 04:10:00
● 2019-03-22 08:40:40
○ 2026-03-17 06:36:30
○ 2026-05-13 17:48:18

○NSns2.bluehost.com2015-11-09 → 2017-02-15 · 4 obs

● 2015-11-09 02:23:44
● 2017-02-15 04:10:00
○ 2019-03-22 08:40:40
○ 2026-05-13 17:48:18

●NSns2.dnsip.com2026-03-17 → 2026-05-13 · 3 obs

○ 2019-03-22 08:40:40
● 2026-03-17 06:36:30
● 2026-05-13 17:48:18

○NSns2.routinesolution.com2019-03-22 → 2019-03-22 · 4 obs

○ 2017-02-15 04:10:00
● 2019-03-22 08:40:40
○ 2026-03-17 06:36:30
○ 2026-05-13 17:48:18

○MXalt1.aspmx.l.google.com2017-02-15 → 2017-02-15 · 4 obs

○ 2016-06-20 02:38:58
● 2017-02-15 04:10:00
○ 2019-03-22 08:40:40
○ 2026-05-13 17:48:18

○MXalt2.aspmx.l.google.com2017-02-15 → 2019-03-22 · 5 obs

○ 2016-06-20 02:38:58
● 2017-02-15 04:10:00
● 2019-03-22 08:40:40
○ 2026-03-17 06:36:30
○ 2026-05-13 17:48:18

○MXalt3.aspmx.l.google.com2017-02-15 → 2017-02-15 · 4 obs

○ 2016-06-20 02:38:58
● 2017-02-15 04:10:00
○ 2019-03-22 08:40:40
○ 2026-05-13 17:48:18

○MXalt4.aspmx.l.google.com2017-02-15 → 2019-03-22 · 5 obs

○ 2016-06-20 02:38:58
● 2017-02-15 04:10:00
● 2019-03-22 08:40:40
○ 2026-03-17 06:36:30
○ 2026-05-13 17:48:18

○MXaspmx.l.google.com2017-02-15 → 2019-03-22 · 5 obs

○ 2016-06-20 02:38:58
● 2017-02-15 04:10:00
● 2019-03-22 08:40:40
○ 2026-03-17 06:36:30
○ 2026-05-13 17:48:18

○MXmail.routinesolution.com2015-11-09 → 2016-06-20 · 4 obs

● 2015-11-09 02:23:44
● 2016-06-20 02:38:58
○ 2017-02-15 04:10:00
○ 2026-05-13 17:48:18

○A162.144.34.302019-03-22 → 2019-03-22 · 4 obs

○ 2017-02-15 04:10:00
● 2019-03-22 08:40:40
○ 2026-03-17 06:36:30
○ 2026-05-13 17:48:18

○A192.163.209.2132017-02-15 → 2017-02-15 · 4 obs

○ 2016-06-20 02:38:58
● 2017-02-15 04:10:00
○ 2019-03-22 08:40:40
○ 2026-05-13 17:48:18

●A35.220.184.1532026-03-17 → 2026-05-13 · 3 obs

○ 2019-03-22 08:40:40
● 2026-03-17 06:36:30
● 2026-05-13 17:48:18

○A50.87.249.612015-11-09 → 2016-06-20 · 4 obs

● 2015-11-09 02:23:44
● 2016-06-20 02:38:58
○ 2017-02-15 04:10:00
○ 2026-05-13 17:48:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
routinesolution.com	ns1.dnsip.com, ns2.dnsip.com	9 records

✅ Authoritative Response

Server:183.253.57.193

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for routinesolution.com (unsigned zone)

⏱️ Timing

Total: 601ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.220.184.153`
NS	2	`ns1.dnsip.com, ns2.dnsip.com`
SOA	1	`ns1.dnsip.com dnsadmin.dnsip.com`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (ns1.dnsip.com, ns1.dnsip.com, ns1.dnsip.com...)

Analysis

Hierarchy

The parent of hostmaster.routinesolution.com is routinesolution.com.

IP Addresses

routinesolution.com points to IP number: 35.220.184.153.

Other host names such as ns1.nethox.com, motiber.code2gether.net, farccursidi.code2gether.net, emma-white.com and phonebookofmadrid.com share IPs with routinesolution.com.

Name Servers

routinesolution.com is delegated to two name servers: ns1.dnsip.com and ns2.dnsip.com.

routinesolution.com shares the same name server setup as 9mp73jg3z3.top, w13721107.com, zjbsj.cn, nbhk.com.cn and tinfloor.com.

routinesolution.com shares some name servers with other domains, for instance urgentgame.com.

Host names with five IPs:

ns2.dnsip.com points to 240e:97d:10:1402:0:1:0:1008, 61.158.128.1, 183.253.57.193, 211.99.99.29 and 211.99.99.33.

Host names with four IPs:

ns1.dnsip.com points to 2001:df2:f080:1::10, 1.193.216.199, 218.98.111.202 and 218.98.111.206.

routinesolution.com - robtex.com