servusfire.com - dns.ninja

`servusfire.com`

DNSSEC	⚠️ Not signed
A	2a02:4780:1d:5933:5d75:8321:645f:b678^{🇺🇸 IIHOS0012a02:4780:1d::/48 HOSTINGER US}
A	2a02:4780:1e:f565:473a:c136:d026:e9ca^{🇺🇸 IIHOS0012a02:4780:1e::/48 HOSTINGER US}
A	191.101.104.106^{🇺🇸 IIHOS001191.101.104.0/24 HOSTINGER US}
A	195.35.60.86^{🇩🇪 IIHOS001195.35.60.0/24}
NS	`ns1.dns-parking.com` ⭐
		A	2400:cb00:2049:1::a29f:18c9^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.201^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dns-parking.com`
NS	`ns2.dns-parking.com`
		A	2400:cb00:2049:1::a29f:192a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.25.42^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dns-parking.com`
MX	`mx1.hostinger.com` ⭐
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx2.hostinger.com`⁽¹⁰⁾
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ns1.dns-parking.com`dns@hostinger.com 2026-07-23 #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=1785060262

Same first word

servusfire.com

DNS History

15 records (8 active, 7 former)

○NSde08undgm01.honeywell.com2015-12-21 → 2017-06-04 · 5 obs

○ 2015-08-22 10:58:26
● 2015-12-21 16:10:10
● 2017-06-04 14:05:06
○ 2026-03-23 12:21:44
○ 2026-07-26 10:22:32

○NSdns1.honeywell.com2015-08-22 → 2017-06-04 · 4 obs

● 2015-08-22 10:58:26
● 2017-06-04 14:05:06
○ 2026-03-23 12:21:44
○ 2026-07-26 10:22:32

○NSdns2.honeywell.com2015-08-22 → 2017-06-04 · 5 obs

● 2015-08-22 10:58:26
○ 2015-12-21 16:10:10
● 2017-06-04 14:05:06
○ 2026-03-23 12:21:44
○ 2026-07-26 10:22:32

●NSns1.dns-parking.com2026-03-23 → 2026-07-26 · 3 obs

○ 2017-06-04 14:05:06
● 2026-03-23 12:21:44
● 2026-07-26 10:22:32

●NSns2.dns-parking.com2026-03-23 → 2026-07-26 · 3 obs

○ 2017-06-04 14:05:06
● 2026-03-23 12:21:44
● 2026-07-26 10:22:32

○MXmail.servusfire.com2015-08-22 → 2017-06-04 · 4 obs

● 2015-08-22 10:58:26
● 2017-06-04 14:05:06
○ 2026-03-23 12:21:44
○ 2026-07-26 10:22:32

●MXmx1.hostinger.com2026-03-23 → 2026-07-26 · 3 obs

○ 2017-06-04 14:05:06
● 2026-03-23 12:21:44
● 2026-07-26 10:22:32

●MXmx2.hostinger.com2026-03-23 → 2026-07-26 · 3 obs

○ 2017-06-04 14:05:06
● 2026-03-23 12:21:44
● 2026-07-26 10:22:32

●A191.101.104.1062026-07-26 → 2026-07-26 · 3 obs

○ 2026-04-02 15:53:40
● 2026-07-26 10:22:30
● 2026-07-26 10:22:32

●A195.35.60.862026-07-26 → 2026-07-26 · 3 obs

○ 2026-04-02 15:53:40
● 2026-07-26 10:22:30
● 2026-07-26 10:22:32

○A199.64.218.302015-08-22 → 2017-06-04 · 4 obs

● 2015-08-22 10:58:26
● 2017-06-04 14:05:06
○ 2026-03-23 12:21:44
○ 2026-07-26 10:22:32

○A2600:1901:0:84ef::2026-03-23 → 2026-04-02 · 5 obs

○ 2017-06-04 14:05:06
● 2026-03-23 12:21:44
● 2026-04-02 15:53:40
○ 2026-07-26 10:22:30
○ 2026-07-26 10:22:32

●A2a02:4780:1d:5933:5d75:8321:645f:b6782026-07-26 → 2026-07-26 · 3 obs

○ 2026-04-02 15:53:40
● 2026-07-26 10:22:30
● 2026-07-26 10:22:32

●A2a02:4780:1e:f565:473a:c136:d026:e9ca2026-07-26 → 2026-07-26 · 3 obs

○ 2026-04-02 15:53:40
● 2026-07-26 10:22:30
● 2026-07-26 10:22:32

○A34.120.137.412026-03-23 → 2026-04-02 · 5 obs

○ 2017-06-04 14:05:06
● 2026-03-23 12:21:44
● 2026-04-02 15:53:40
○ 2026-07-26 10:22:30
○ 2026-07-26 10:22:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
servusfire.com	ns1.dns-parking.com, ns2.dns-parking.com	4 records

✅ Authoritative Response

Server:162.159.25.42

NS records: ns1.dns-parking.com, ns2.dns-parking.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for servusfire.com (unsigned zone)

⏱️ Timing

Total: 165ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`195.35.60.226, 191.96.144.109`
AAAA	2	`2a02:4780:1d:d264:4443:4bdc:6115:4a2c, 2a02:4780:1e:5248:4f92:d697:358c:44e`
NS	2	`ns1.dns-parking.com, ns2.dns-parking.com`
MX	2	`mx1.hostinger.com (pri: 5), mx2.hostinger.com (pri: 10)`
SOA	1	`ns1.dns-parking.com dns.hostinger.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.dns-parking.com, ns1.dns-parking.com, ns2.dns-parking.com...)

Analysis

IP Addresses

servusfire.com resolves to four IP addresses: 191.101.104.106, 195.35.60.86, 2a02:4780:1d:5933:5d75:8321:645f:b678 and 2a02:4780:1e:f565:473a:c136:d026:e9ca.

estruturainfo.com.br, vaporwaveboutique.com, lsrsa.edu.in plus two other host names have IP numbers in common with servusfire.com.

Name Servers

servusfire.com is delegated to two name servers: ns1.dns-parking.com and ns2.dns-parking.com.

The name server configuration of servusfire.com is shared with other domains, for instance dmfpresales.com, meshnova.com, kirang.com and two others.

servusfire.com shares at least some of its name servers with other domains, such as tapsa.com.ar.

ns1.dns-parking.com and ns2.dns-parking.com each resolve to two IP addresses: ns1.dns-parking.com points to 162.159.24.201 and 2400:cb00:2049:1::a29f:18c9, while ns2.dns-parking.com points to 162.159.25.42 and 2400:cb00:2049:1::a29f:192a.

Mail Servers

servusfire.com uses two mail servers, mx1.hostinger.com and mx2.hostinger.com.

The mail server setup of servusfire.com matches that of other domains such as foreverjackets.com, baapcompany.com, thayyilsports.com and two others.

servusfire.com has mail servers in common with other domains — for example eaglytics-co.com and satech.in.

mx1.hostinger.com and mx2.hostinger.com each resolve to two IP addresses: 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f.

mx1.hostinger.com and mx2.hostinger.com are host names that each point to 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.com and mx2.hostinger.com are host names that each point to 172.65.182.103 IP addresses.