currentcms.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

currentcms.com

com

WOT: SAFE (60/100)

Same first word

Similar names

Previous names

Next names

DNS History

13 records (3 active, 10 former)

20162017201820192020202120222023202420252026NSns71.domaincontrol.comns72.domaincontrol.comdns1.stabletransit.comdns2.stabletransit.comns.rackspace.comns1626.ztomy.comns2626.ztomy.comMXmxa.mailgun.orgmxb.mailgun.orgA64.23.159.188166.78.17.222204.11.56.48PTRns1626.ztomy.com
○NSdns1.stabletransit.com2015-07-09 → 2017-02-01 · 4 obs
● 2015-07-09 19:18:34
● 2017-02-01 18:51:58
○ 2018-10-17 09:35:36
○ 2026-10-26 15:48:48
○NSdns2.stabletransit.com2015-07-09 → 2017-02-01 · 4 obs
● 2015-07-09 19:18:34
● 2017-02-01 18:51:58
○ 2018-10-17 09:35:36
○ 2026-10-26 15:48:48
○NSns.rackspace.com2015-07-09 → 2017-02-01 · 4 obs
● 2015-07-09 19:18:34
● 2017-02-01 18:51:58
○ 2018-10-17 09:35:36
○ 2026-10-26 15:48:48
○NSns1626.ztomy.com2018-10-17 → 2018-10-17 · 4 obs
○ 2017-02-01 18:51:58
● 2018-10-17 09:35:36
○ 2026-09-18 19:33:04
○ 2026-10-26 15:48:48
○NSns2626.ztomy.com2018-10-17 → 2018-10-17 · 4 obs
○ 2017-02-01 18:51:58
● 2018-10-17 09:35:36
○ 2026-09-18 19:33:04
○ 2026-10-26 15:48:48
●NSns71.domaincontrol.com2026-09-18 → 2026-10-26 · 3 obs
○ 2018-10-17 09:35:36
● 2026-09-18 19:33:04
● 2026-10-26 15:48:48
●NSns72.domaincontrol.com2026-09-18 → 2026-10-26 · 3 obs
○ 2018-10-17 09:35:36
● 2026-09-18 19:33:04
● 2026-10-26 15:48:48
○MXmxa.mailgun.org2015-07-09 → 2017-02-01 · 4 obs
● 2015-07-09 19:18:34
● 2017-02-01 18:51:58
○ 2018-10-17 09:35:36
○ 2026-10-26 15:48:48
○MXmxb.mailgun.org2015-07-09 → 2017-02-01 · 4 obs
● 2015-07-09 19:18:34
● 2017-02-01 18:51:58
○ 2018-10-17 09:35:36
○ 2026-10-26 15:48:48
○A166.78.17.2222015-07-09 → 2017-02-01 · 4 obs
● 2015-07-09 19:18:34
● 2017-02-01 18:51:58
○ 2018-10-17 09:35:36
○ 2026-10-26 15:48:48
○A204.11.56.482018-10-17 → 2018-10-17 · 4 obs
○ 2017-02-01 18:51:58
● 2018-10-17 09:35:36
○ 2026-09-18 19:33:04
○ 2026-10-26 15:48:48
●A64.23.159.1882026-09-18 → 2026-10-26 · 3 obs
○ 2018-10-17 09:35:36
● 2026-09-18 19:33:04
● 2026-10-26 15:48:48
○PTRns1626.ztomy.com2018-10-17 → 2018-10-17 · 3 obs
● 2018-10-17 09:35:36
○ 2026-09-18 19:33:04
○ 2026-10-26 15:48:48

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, l.gtld-servers.net...-
currentcms.comns71.domaincontrol.com, ns72.domaincontrol.com4 records

✅ Authoritative Response

Server:97.74.105.46

NS records: ns71.domaincontrol.com, ns72.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for currentcms.com (unsigned zone)

⏱️ Timing

Total: 605ms | Queries: -

📄 Records

TypeCountSample Data
A164.23.159.188
NS2ns71.domaincontrol.com, ns72.domaincontrol.com
SOA1ns71.domaincontrol.com dns.jomax.net

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns71.domaincontrol.com, ns71.domaincontrol.com, ns72.domaincontrol.com...)

Analysis

IP Addresses

currentcms.com has exactly one IP address — 64.23.159.188.

Name Servers

currentcms.com has two authoritative name servers — ns71.domaincontrol.com and ns72.domaincontrol.com.

The name server configuration of currentcms.com is shared with other domains, for instance expressonwheels.com, kbkaquafarms.com, velocityofconsumption.com and two others.

Both ns71.domaincontrol.com and ns72.domaincontrol.com have two IP addresses each. ns71.domaincontrol.com resolves to 97.74.105.46 and 2603:5:2194::2e; ns72.domaincontrol.com resolves to 173.201.73.46 and 2603:5:2294::2e.