solved.how - robtex.com
solved.how
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 192.227.177.112🇺🇸 Colocrossing-AS192.227.176.0/22 | ||||||
| PTR | 192-227-177-112-host.colocrossing.com | ||||||
| NS | ns1.openprovider.nl ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a0a🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.10Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.openprovider.be | ||||||
| A | 2400:cb00:2049:1::a29f:1b60🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.96Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns3.openprovider.eu | ||||||
| A | 2400:cb00:2049:1::a29f:3059🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.48.89Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.openprovider.nldns@openprovider.eu 2024-05-05 #4 | ||||||
how
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
DNS History
5 records (4 active, 1 former)
●NSns1.openprovider.nl2016-12-10 → 2026-07-04 · 2 obs
● 2026-07-04 04:50:26
●NSns2.openprovider.be2016-12-10 → 2026-07-04 · 2 obs
● 2026-07-04 04:50:26
●NSns3.openprovider.eu2016-12-10 → 2026-07-04 · 2 obs
● 2026-07-04 04:50:26
●A192.227.177.1122026-02-23 → 2026-07-04 · 3 obs
● 2026-02-23 13:05:50
● 2026-07-04 04:50:26
○A95.170.88.772016-12-10 → 2021-09-14 · 4 obs
● 2021-09-14 11:09:24
○ 2026-02-23 13:05:50
○ 2026-07-04 04:50:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com... | 10 records |
| solved.how | ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu | - |
✅ Authoritative Response
Server:162.159.27.96
NS records: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1952ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.227.177.112 |
| NS | 3 | ns3.openprovider.eu, ns1.openprovider.nl... |
| SOA | 1 | ns1.openprovider.nl dns.openprovider.eu |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld4.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)
Analysis
IP Addresses
solved.how resolves to just one IP address, 192.227.177.112.
Two other host names, along with web-id.com, v0te.com and e-id.eu, also share IP numbers with solved.how.
Name Servers
DNS for solved.how is handled by three authoritative name servers: ns2.openprovider.be, ns3.openprovider.eu and ns1.openprovider.nl.
solved.how has at least partial name server overlap with other domains, such as alteco-europe.org, brouwerseiland.com, pelatis.nl and two others.
Three hostnames — ns2.openprovider.be, ns3.openprovider.eu and ns1.openprovider.nl — each have two IP addresses: ns2.openprovider.be has 162.159.27.96 and 2400:cb00:2049:1::a29f:1b60, ns3.openprovider.eu has 162.159.48.89 and 2400:cb00:2049:1::a29f:3059, and ns1.openprovider.nl has 162.159.26.10 and 2400:cb00:2049:1::a29f:1a0a.