cirmf.com - dns.ninja

cirmf.com

DNSSEC⚠️ Not signed
A183.136.138.175🇨🇳 CHINATELECOM-ZHEJIANG-NINGBO-IDC183.136.138.0/24 Chinanet-NingBo-IDC
NSns1.julydns.com ⭐
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.julydns.com
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
SOAns1.julydns.commaster@jmdns.com serial=1782994608

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1786093829
WOT: SAFE (1/100)

Same first word

cirmf.com
cirmf.org

Similar names

icfrm.org
ircfm.de
micrf.xyz
fcmri.net
cfmir.com
cmfri.org.in
ifcrm.se
mcfri.ch
rcfmi.com
cimfr.nic.in
cfirm.co
cmfri.org
icrfm.com
fmcri.com
ficrm.com
icrfm.co.uk
mrfic.com
cmifr.com
mcfir.com
fmric.or.jp
cimfr.res.in
icfmr.com
rficm.com
fcmir.com.ua
mirfc.com.mx
mirfc.de
fcmri.com
cfirm.com
cfimr.com
crifm.org
cfirm.ru
ifcrm.com
mirfc.com
cmfri.com
crmfi.com
rmcfi.com
fimcr.com
rfcim.com

DNS History

19 records (3 active, 16 former)

20162017201820192020202120222023202420252026NSns1.julydns.comns2.julydns.comns1.namebrightdns.comnsg1.namebrightdns.comnsg2.namebrightdns.comnst1.namebrightdns.comnst2.namebrightdns.comMXanmail.namebrightmail.comA183.136.138.17534.199.151.16352.0.96.2452.20.154.352.200.243.12352.71.117.9954.152.144.24354.174.31.25454.208.74.215CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.comhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com
●NSns1.julydns.com2026-04-13 → 2026-08-07 · 3 obs
○ 2017-02-15 13:34:22
● 2026-04-13 14:05:58
● 2026-08-07 09:23:18
○NSns1.namebrightdns.com2015-11-10 → 2016-05-29 · 5 obs
○ 2015-07-01 01:46:34
● 2015-11-10 09:02:10
● 2016-05-29 23:55:14
○ 2017-02-15 13:34:22
○ 2026-08-07 09:23:18
●NSns2.julydns.com2026-04-13 → 2026-08-07 · 3 obs
○ 2017-02-15 13:34:22
● 2026-04-13 14:05:58
● 2026-08-07 09:23:18
○NSnsg1.namebrightdns.com2015-07-01 → 2016-05-29 · 5 obs
● 2015-07-01 01:46:34
○ 2015-11-10 09:02:10
● 2016-05-29 23:55:14
○ 2017-02-15 13:34:22
○ 2026-08-07 09:23:18
○NSnsg2.namebrightdns.com2015-07-01 → 2016-05-29 · 4 obs
● 2015-07-01 01:46:34
● 2016-05-29 23:55:14
○ 2017-02-15 13:34:22
○ 2026-08-07 09:23:18
○NSnst1.namebrightdns.com2017-02-15 → 2017-02-15 · 4 obs
○ 2016-05-29 23:55:14
● 2017-02-15 13:34:22
○ 2026-04-13 14:05:58
○ 2026-08-07 09:23:18
○NSnst2.namebrightdns.com2017-02-15 → 2017-02-15 · 4 obs
○ 2016-05-29 23:55:14
● 2017-02-15 13:34:22
○ 2026-04-13 14:05:58
○ 2026-08-07 09:23:18
○MXanmail.namebrightmail.com2015-07-01 → 2015-07-01 · 3 obs
● 2015-07-01 01:46:34
○ 2015-11-10 09:02:10
○ 2026-08-07 09:23:18
●A183.136.138.1752026-04-13 → 2026-08-07 · 3 obs
○ 2017-02-15 13:34:22
● 2026-04-13 14:05:58
● 2026-08-07 09:23:18
○A34.199.151.1632017-02-15 → 2017-02-15 · 4 obs
○ 2016-05-29 23:55:14
● 2017-02-15 13:34:22
○ 2026-04-13 14:05:58
○ 2026-08-07 09:23:18
○A52.0.96.242016-02-07 → 2016-02-07 · 4 obs
○ 2015-11-10 09:02:10
● 2016-02-07 08:49:36
○ 2016-05-29 23:55:14
○ 2026-08-07 09:23:18
○A52.20.154.32017-02-15 → 2017-02-15 · 4 obs
○ 2016-05-29 23:55:14
● 2017-02-15 13:34:22
○ 2026-04-13 14:05:58
○ 2026-08-07 09:23:18
○A52.200.243.1232016-05-29 → 2016-05-29 · 4 obs
○ 2016-02-07 08:49:36
● 2016-05-29 23:55:14
○ 2017-02-15 13:34:22
○ 2026-08-07 09:23:18
○A52.71.117.992016-02-07 → 2016-02-07 · 4 obs
○ 2015-11-10 09:02:10
● 2016-02-07 08:49:36
○ 2016-05-29 23:55:14
○ 2026-08-07 09:23:18
○A54.152.144.2432016-05-29 → 2016-05-29 · 4 obs
○ 2016-02-07 08:49:36
● 2016-05-29 23:55:14
○ 2017-02-15 13:34:22
○ 2026-08-07 09:23:18
○A54.174.31.2542015-07-01 → 2015-11-10 · 4 obs
● 2015-07-01 01:46:34
● 2015-11-10 09:02:10
○ 2016-02-07 08:49:36
○ 2026-08-07 09:23:18
○A54.208.74.2152015-07-01 → 2015-11-10 · 4 obs
● 2015-07-01 01:46:34
● 2015-11-10 09:02:10
○ 2016-02-07 08:49:36
○ 2026-08-07 09:23:18
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-07-01 → 2016-05-29 · 4 obs
● 2015-07-01 01:46:34
● 2016-05-29 23:55:14
○ 2017-02-15 13:34:22
○ 2026-08-07 09:23:18
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-02-15 → 2017-02-15 · 4 obs
○ 2016-05-29 23:55:14
● 2017-02-15 13:34:22
○ 2026-04-13 14:05:58
○ 2026-08-07 09:23:18

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
cirmf.comns1.julydns.com, ns2.julydns.com2 records

✅ Authoritative Response

Server:162.159.48.223

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cirmf.com (unsigned zone)

⏱️ Timing

Total: 1204ms | Queries: -

📄 Records

TypeCountSample Data
A1183.136.138.175
NS2ns1.julydns.com, ns2.julydns.com
SOA1ns1.julydns.com master.jmdns.com

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

cirmf.com resolves to just one IP address, 183.136.138.175.

Two other host names, along with bbly88888.com, shcxprint.com and 56tengda.com, also share IP numbers with cirmf.com.

Name Servers

cirmf.com uses two name servers for its delegation: ns1.julydns.com and ns2.julydns.com.

cirmf.com shares its NS records with other domains, for example 0833fs.com, haotianjdwx.com, qfpwpv.cn and two others.

cirmf.com has at least partial name server overlap with other domains, such as xnweb.com.cn, k3233.com, jindian99.com and two others.

It is common to find these name servers paired with the name servers ns1.judns.com, ns2.judns.com, ns1.onclouddns.com and ns2.onclouddns.com.

ns1.julydns.com resolves to 162.159.48.223; ns2.julydns.com resolves to the same IP address, 162.159.48.223.

Both ns1.julydns.com and ns2.julydns.com resolve to 162.159.48.223 IP addresses each.