krxe.com - dns.ninja
krxe.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.domainmanage.com ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::adf5:3b04🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 173.245.59.4🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.domainmanage.com ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::c629:df27🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 198.41.223.39Cloudflare198.41.223.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | cf-198-41-223-39.cloudflare.com | ||||||
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.netnstld@verisign-grs.com serial=1783666567 | ||||||
Same first word
Similar names
DNS History
14 records (2 active, 12 former)
○NSbuy.internettraffic.com2015-08-13 → 2016-07-11 · 4 obs
● 2015-08-13 21:27:18
● 2016-07-11 21:11:02
○ 2017-03-19 12:46:44
○ 2026-07-10 07:06:00
● 2016-07-11 21:11:02
○ 2017-03-19 12:46:44
○ 2026-07-10 07:06:00
○NSns1.afternic.com2026-03-26 → 2026-04-03 · 5 obs
○ 2020-03-21 02:43:02
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
●NSns1.domainmanage.com2026-07-04 → 2026-07-10 · 3 obs
○ 2026-04-03 21:34:36
● 2026-07-04 19:49:36
● 2026-07-10 07:06:00
● 2026-07-04 19:49:36
● 2026-07-10 07:06:00
○NSns1.uniregistrymarket.link2017-03-19 → 2020-03-21 · 5 obs
○ 2016-07-11 21:11:02
● 2017-03-19 12:46:44
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
● 2017-03-19 12:46:44
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○NSns2.afternic.com2026-03-26 → 2026-04-03 · 5 obs
○ 2020-03-21 02:43:02
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
●NSns2.domainmanage.com2026-07-04 → 2026-07-10 · 3 obs
○ 2026-04-03 21:34:36
● 2026-07-04 19:49:36
● 2026-07-10 07:06:00
● 2026-07-04 19:49:36
● 2026-07-10 07:06:00
○NSns2.uniregistrymarket.link2017-03-19 → 2020-03-21 · 5 obs
○ 2016-07-11 21:11:02
● 2017-03-19 12:46:44
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
● 2017-03-19 12:46:44
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○NSsell.internettraffic.com2015-08-13 → 2016-07-11 · 4 obs
● 2015-08-13 21:27:18
● 2016-07-11 21:11:02
○ 2017-03-19 12:46:44
○ 2026-07-10 07:06:00
● 2016-07-11 21:11:02
○ 2017-03-19 12:46:44
○ 2026-07-10 07:06:00
○MXmx247.in-mx.com2020-03-21 → 2020-03-21 · 3 obs
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○MXmx247.in-mx.net2020-03-21 → 2020-03-21 · 3 obs
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○A13.248.169.482026-03-26 → 2026-04-03 · 5 obs
○ 2020-03-21 02:43:02
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
○A69.172.201.1532016-07-11 → 2020-03-21 · 5 obs
○ 2016-03-16 14:38:44
● 2016-07-11 21:11:02
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
● 2016-07-11 21:11:02
● 2020-03-21 02:43:02
○ 2026-03-26 21:59:14
○ 2026-07-10 07:06:00
○A69.172.201.2082015-08-13 → 2016-03-16 · 4 obs
● 2015-08-13 21:27:18
● 2016-03-16 14:38:44
○ 2016-07-11 21:11:02
○ 2026-07-10 07:06:00
● 2016-03-16 14:38:44
○ 2016-07-11 21:11:02
○ 2026-07-10 07:06:00
○A76.223.54.1462026-03-26 → 2026-04-03 · 5 obs
○ 2020-03-21 02:43:02
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
● 2026-03-26 21:59:14
● 2026-04-03 21:34:36
○ 2026-07-04 19:49:36
○ 2026-07-10 07:06:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| krxe.com | ns1.domainmanage.com, ns2.domainmanage.com | 2 records |
✅ Authoritative Response
Server:173.245.59.4
NS records: ns1.domainmanage.com, ns2.domainmanage.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for krxe.com (unsigned zone)
⏱️ Timing
Total: 94ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainmanage.com, ns2.domainmanage.com)
Analysis
Name Servers
krxe.com has two authoritative name servers — ns1.domainmanage.com and ns2.domainmanage.com.
krxe.com shares its name server setup with other domains, including menumeal.com, fluentc.com, gitgel.com and two others.
Both ns1.domainmanage.com and ns2.domainmanage.com have two IP addresses each. ns1.domainmanage.com resolves to 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04; ns2.domainmanage.com resolves to 198.41.223.39 and 2400:cb00:2049:1::c629:df27.