chromiumm.com - robtex.com
chromiumm.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=1771291435 | ||||||
DNS History
13 records (6 active, 7 former)
○NSns1.beget.com2020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
○NSns1.beget.pro2020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
●NSns1.cloudns.net2026-03-12 → 2026-03-12 · 3 obs
● 2026-03-12 15:08:04
● 2026-03-12 15:08:08
○NSns2.beget.com2020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
○NSns2.beget.pro2020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
●NSpns1.cloudns.net2026-03-12 → 2026-03-12 · 3 obs
● 2026-03-12 15:08:04
● 2026-03-12 15:08:08
●NSpns2.cloudns.net2026-03-12 → 2026-03-12 · 3 obs
● 2026-03-12 15:08:04
● 2026-03-12 15:08:08
●NSpns3.cloudns.net2026-03-12 → 2026-03-12 · 3 obs
● 2026-03-12 15:08:04
● 2026-03-12 15:08:08
●NSpns4.cloudns.net2026-03-12 → 2026-03-12 · 3 obs
● 2026-03-12 15:08:04
● 2026-03-12 15:08:08
○MXmx1.beget.com2020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
○MXmx2.beget.com2020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
○A87.236.16.32020-02-06 → 2020-02-06 · 3 obs
○ 2026-03-12 15:08:04
○ 2026-03-12 15:08:08
●A91.240.87.2312026-03-12 → 2026-03-12 · 3 obs
● 2026-03-12 15:08:04
● 2026-03-12 15:08:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| chromiumm.com | pns2.cloudns.net, pns1.cloudns.net, pns3.cloudns.net, pns4.cloudns.net | - |
✅ Authoritative Response
Server: 185.136.97.111
NS records: pns2.cloudns.net, pns1.cloudns.net, pns3.cloudns.net, pns4.cloudns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for chromiumm.com (unsigned zone)
⏱️ Timing
Total: 2367ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.240.87.231 |
| NS | 4 | pns2.cloudns.net, pns4.cloudns.net... |
| TXT | 3 | v=spf1 -all, afternic-verification-4kMWVDb5tXpvkxfkPM... |
| SOA | 1 | ns1.cloudns.net support.cloudns.net |
Analysis
IP Addresses
chromiumm.com resolves to one IP number: 91.240.87.231.
other host names including forbau.ru, ishtory.ru, nobat.ru, aktei.ru and fasadoved.ru share IP numbers with chromiumm.com.
Name Servers
chromiumm.com is delegated to five name servers: ns1.cloudns.net, pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net and pns4.cloudns.net.
chromiumm.com at least partially shares name servers with other domains, for instance biopharmacr.com, data-express.ch, 190.102.239.104.in-addr.arpa, ffhs.org.uk and babiczky.hu.
Name servers commonly used together include ns2.cloudns.net, ns4.cloudns.net, ns3.cloudns.net, pns6.cloudns.net, pns5.cloudns.net, pns7.cloudns.net, pns8.cloudns.net, pns9.cloudns.net and pns10.cloudns.net.
Host names with two IP numbers:
ns1.cloudns.net points to 2a00:1768:1001:9::1 and 85.159.233.17
pns1.cloudns.net points to 2a06:fb00:1::1:111 and 185.136.96.111
pns2.cloudns.net points to 2a06:fb00:1::2:111 and 185.136.97.111
pns3.cloudns.net points to 2a06:fb00:1::3:111 and 185.136.98.111
pns4.cloudns.net points to 2a06:fb00:1::4:111 and 185.136.99.111