fmfire.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status

fmfire.com

com

Previously NS for

Previously MX for

Same first word

Similar names

DNS History

17 records (5 active, 12 former)

20162017201820192020202120222023202420252026NSns1.afternic.comns2.afternic.comverification-d3jclucsp89ganyqbydeny.ns101.verify.hndns01.muumuu-domain.comdns02.muumuu-domain.comfmfire.commaster.dns.ne.jpns1.dns.ne.jpns1626.ztomy.comns2.dns.ne.jpns2626.ztomy.comMXfmfire.comA13.248.169.4876.223.54.146204.11.56.48219.94.129.63PTRns1626.ztomy.com
NSdns01.muumuu-domain.com2015-10-27 → 2015-10-27 · 3 obs
● 2015-10-27 18:47:08
○ 2016-02-25 04:57:42
○ 2026-08-17 10:23:22
NSdns02.muumuu-domain.com2015-10-27 → 2015-10-27 · 3 obs
● 2015-10-27 18:47:08
○ 2016-02-25 04:57:42
○ 2026-08-17 10:23:22
NSfmfire.com2015-10-27 → 2015-10-27 · 3 obs
● 2015-10-27 18:47:08
○ 2016-02-25 04:57:42
○ 2026-08-17 10:23:22
NSmaster.dns.ne.jp2016-02-25 → 2016-07-08 · 5 obs
○ 2015-10-27 18:47:08
● 2016-02-25 04:57:42
● 2016-07-08 03:52:34
○ 2017-02-09 12:44:08
○ 2026-08-17 10:23:22
NSns1.afternic.com2026-08-15 → 2026-08-17 · 3 obs
○ 2019-02-04 20:37:36
● 2026-08-15 02:26:38
● 2026-08-17 10:23:22
NSns1.dns.ne.jp2016-02-25 → 2016-07-08 · 5 obs
○ 2015-10-27 18:47:08
● 2016-02-25 04:57:42
● 2016-07-08 03:52:34
○ 2017-02-09 12:44:08
○ 2026-08-17 10:23:22
NSns1626.ztomy.com2017-02-09 → 2017-02-09 · 4 obs
○ 2016-07-08 03:52:34
● 2017-02-09 12:44:08
○ 2019-02-04 20:37:36
○ 2026-08-17 10:23:22
NSns2.afternic.com2026-08-15 → 2026-08-17 · 3 obs
○ 2019-02-04 20:37:36
● 2026-08-15 02:26:38
● 2026-08-17 10:23:22
NSns2.dns.ne.jp2016-02-25 → 2016-07-08 · 5 obs
○ 2015-10-27 18:47:08
● 2016-02-25 04:57:42
● 2016-07-08 03:52:34
○ 2017-02-09 12:44:08
○ 2026-08-17 10:23:22
NSns2626.ztomy.com2017-02-09 → 2017-02-09 · 4 obs
○ 2016-07-08 03:52:34
● 2017-02-09 12:44:08
○ 2019-02-04 20:37:36
○ 2026-08-17 10:23:22
NSverification-d3jclucsp89ganyqbydeny.ns101.verify.hn2026-08-15 → 2026-08-17 · 3 obs
○ 2019-02-04 20:37:36
● 2026-08-15 02:26:38
● 2026-08-17 10:23:22
MXfmfire.com2016-02-25 → 2016-07-08 · 4 obs
● 2016-02-25 04:57:42
● 2016-07-08 03:52:34
○ 2017-02-09 12:44:08
○ 2026-08-17 10:23:22
A13.248.169.482026-08-15 → 2026-08-17 · 3 obs
○ 2019-02-04 20:37:36
● 2026-08-15 02:26:38
● 2026-08-17 10:23:22
A204.11.56.482017-02-09 → 2017-02-09 · 4 obs
○ 2016-07-08 03:52:34
● 2017-02-09 12:44:08
○ 2019-02-04 20:37:36
○ 2026-08-17 10:23:22
A219.94.129.632016-02-25 → 2016-07-08 · 4 obs
● 2016-02-25 04:57:42
● 2016-07-08 03:52:34
○ 2017-02-09 12:44:08
○ 2026-08-17 10:23:22
A76.223.54.1462026-08-15 → 2026-08-17 · 3 obs
○ 2019-02-04 20:37:36
● 2026-08-15 02:26:38
● 2026-08-17 10:23:22
PTRns1626.ztomy.com2017-02-09 → 2017-02-09 · 3 obs
● 2017-02-09 12:44:08
○ 2019-02-04 20:37:36
○ 2026-08-17 10:23:22

🔍 DNS Trace

Analysis

IP Addresses

fmfire.com directs to two IP numbers, 13.248.169.48 and 76.223.54.146

Additional host names — mx.globalrivers.com, investergpt.xyz, buildprogroup.com and two others — share IP numbers with fmfire.com.

Name Servers

fmfire.com has three name servers — ns1.afternic.com, ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

fmfire.com has at least partial name server overlap with other domains, such as hatdieurangmuoi.com, host14-204.matrixconsulting.net, robots.solutions.ucpag.com and two others.

These name servers tend to appear together with the name servers verification-q2yfbmuxrvnsdnaogqtqft.ns101.verify.hn, verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn and verification-urj2ap2akmgcchkhharttb.ns101.verify.hn.

Each of ns1.afternic.com, ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn points to two IP numbers. ns1.afternic.com points to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45. verification-d3jclucsp89ganyqbydeny.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146.