faremonitor.com - dns.ninja

`faremonitor.com`

DNSSEC	⚠️ Not signed
A	162.241.217.237^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
		PTR	`box5520.bluehost.com`
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.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:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.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	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 ip4:162.241.217.237 a mx include:websitewelcome.com ~all`
SOA	`ns1.bluehost.com`root@box5520.bluehost.com 2026-08-06 #0

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

Same first word

faremonitor.com

Similar names

DNS History

19 records (8 active, 11 former)

●NSns1.bluehost.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

○NSns1.dsredirection.com2008-03-20 → 2017-01-23 · 4 obs

● 2008-03-20 06:52:58
● 2017-01-23 00:05:42
○ 2020-02-15 10:13:18
○ 2026-08-09 13:09:16

○NSns1.parkingcrew.net2020-02-15 → 2020-02-15 · 4 obs

○ 2017-01-23 00:05:42
● 2020-02-15 10:13:18
○ 2026-04-05 17:01:02
○ 2026-08-09 13:09:16

●NSns2.bluehost.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

○NSns2.dsredirection.com2008-03-20 → 2017-01-23 · 4 obs

● 2008-03-20 06:52:58
● 2017-01-23 00:05:42
○ 2020-02-15 10:13:18
○ 2026-08-09 13:09:16

○NSns2.parkingcrew.net2020-02-15 → 2020-02-15 · 4 obs

○ 2017-01-23 00:05:42
● 2020-02-15 10:13:18
○ 2026-04-05 17:01:02
○ 2026-08-09 13:09:16

●MXalt1.aspmx.l.google.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

●MXalt2.aspmx.l.google.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

●MXalt3.aspmx.l.google.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

●MXalt4.aspmx.l.google.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

●MXaspmx.l.google.com2026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

○MXmail.h-email.net2020-02-15 → 2020-02-15 · 3 obs

● 2020-02-15 10:13:18
○ 2026-04-05 17:01:02
○ 2026-08-09 13:09:16

●A162.241.217.2372026-04-05 → 2026-08-09 · 3 obs

○ 2020-02-15 10:13:18
● 2026-04-05 17:01:02
● 2026-08-09 13:09:16

○A185.53.178.62020-02-15 → 2020-02-15 · 4 obs

○ 2017-01-23 00:05:42
● 2020-02-15 10:13:18
○ 2026-04-05 17:01:02
○ 2026-08-09 13:09:16

○A208.73.210.2002015-07-25 → 2017-01-23 · 5 obs

○ 2008-03-20 06:52:58
● 2015-07-25 02:49:26
● 2017-01-23 00:05:42
○ 2020-02-15 10:13:18
○ 2026-08-09 13:09:16

○A208.73.210.2142015-07-25 → 2017-01-23 · 5 obs

○ 2008-03-20 06:52:58
● 2015-07-25 02:49:26
● 2017-01-23 00:05:42
○ 2020-02-15 10:13:18
○ 2026-08-09 13:09:16

○A208.73.210.2172015-07-25 → 2017-01-23 · 5 obs

○ 2008-03-20 06:52:58
● 2015-07-25 02:49:26
● 2017-01-23 00:05:42
○ 2020-02-15 10:13:18
○ 2026-08-09 13:09:16

○A208.73.211.1782015-07-25 → 2017-01-23 · 5 obs

○ 2008-03-20 06:52:58
● 2015-07-25 02:49:26
● 2017-01-23 00:05:42
○ 2020-02-15 10:13:18
○ 2026-08-09 13:09:16

○PTRns1.dsredirection.com2017-01-23 → 2017-01-23 · 3 obs

● 2017-01-23 00:05:42
○ 2026-04-05 17:01:02
○ 2026-08-09 13:09:16

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:162.159.25.175

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for faremonitor.com (unsigned zone)

⏱️ Timing

Total: 442ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.241.217.237`
NS	2	`ns2.bluehost.com, ns1.bluehost.com`
MX	5	`alt3.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...`
TXT	1	`v=spf1 ip4:162.241.217.237 a mx include:`
SOA	1	`ns1.bluehost.com root.box5520.bluehost.c`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

faremonitor.com resolves to one IP address: 162.241.217.237.

mail.mikeisgood.com, mail.digitalminbar.com, koszalka.com and two other host names share IP numbers with faremonitor.com.

Name Servers

DNS delegation for faremonitor.com points to two name servers: ns1.bluehost.com and ns2.bluehost.com.

faremonitor.com uses the same name servers as several other domains — among them apindy.com, bibledetective.com, stampinwithmarianne.com and two more.

At least some of faremonitor.com's name servers are shared with other domains, for example toposla.com and rossi.co.uk.

Each of ns1.bluehost.com and ns2.bluehost.com has one IP address: ns1.bluehost.com uses 162.159.24.80 and ns2.bluehost.com uses 162.159.25.175.

Mail Servers

faremonitor.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

faremonitor.com has at least partial mail server overlap with other domains such as ns500759.ns500758.ns500698.ns500758.ns500736.ns500708.ns500686.ns500652.ns500576.trackreceptor.com, ns500765.ns500693.ns500734.ns500699.ns500693.ns500699.ns500734.ns500693.ns500588.ns500683.ns500632.ns500588.ns500588.ns500588.ns500588.dtrkdll.com, ns500759.ns500758.ns500758.ns500698.ns500736.ns500736.ns500576.ns500576.ns500576.ns500576.ns500708.trackreceptor.com and two more.

The mail servers alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com has two IP addresses: 172.253.122.26 and 2607:f8b0:4004:c1d::1a.

alt1.aspmx.l.google.com has two IP addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com has two IP addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com has two IP addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.