whatcould.be - robtex.com
whatcould.be
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns3.afternic.com ⭐ | ||||||
| A | 97.74.98.65🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns3.afternic.com | ||||||
| NS | ns4.afternic.com | ||||||
| A | 173.201.66.65🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns4.namefind.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns3.afternic.comdns@jomax.net 2025-10-01 #0 | ||||||
be
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nsset.be ⭐ | ||||||
| NS | b.nsset.be | ||||||
| NS | c.nsset.be | ||||||
| NS | d.nsset.be | ||||||
| NS | y.nsset.be | ||||||
| NS | z.nsset.be | ||||||
| SOA | a.nsset.bebe-hostmaster@dnsbelgium.be serial=1028240207 | ||||||
Same first word
whatcould.be |
whatcould.com |
Similar names
DNS History
9 records (4 active, 5 former)
○NSns15.domaincontrol.com2015-07-01 → 2018-07-26 · 4 obs
● 2018-07-26 02:32:22
○ 2026-04-03 14:17:28
○ 2026-04-05 20:01:42
○NSns16.domaincontrol.com2015-07-01 → 2018-07-26 · 4 obs
● 2018-07-26 02:32:22
○ 2026-04-03 14:17:28
○ 2026-04-05 20:01:42
●NSns3.afternic.com2026-04-03 → 2026-04-05 · 3 obs
● 2026-04-03 14:17:28
● 2026-04-05 20:01:42
●NSns4.afternic.com2026-04-03 → 2026-04-05 · 3 obs
● 2026-04-03 14:17:28
● 2026-04-05 20:01:42
○MXmail.whatcould.be2015-07-01 → 2018-07-26 · 4 obs
● 2018-07-26 02:32:22
○ 2026-04-03 14:17:28
○ 2026-04-05 20:01:42
●A13.248.169.482026-04-03 → 2026-04-05 · 3 obs
● 2026-04-03 14:17:28
● 2026-04-05 20:01:42
○A160.153.41.32015-07-01 → 2015-07-01 · 3 obs
○ 2015-11-19 11:27:18
○ 2026-04-05 20:01:42
○A162.242.212.1302015-11-19 → 2018-07-26 · 5 obs
● 2015-11-19 11:27:18
● 2018-07-26 02:32:22
○ 2026-04-03 14:17:28
○ 2026-04-05 20:01:42
●A76.223.54.1462026-04-03 → 2026-04-05 · 3 obs
● 2026-04-03 14:17:28
● 2026-04-05 20:01:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| be | a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be... | - |
| whatcould.be | ns3.afternic.com, ns4.afternic.com | - |
✅ Authoritative Response
Server:97.74.98.65
NS records: ns3.afternic.com, ns4.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whatcould.be (unsigned zone)
⏱️ Timing
Total: 575ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns3.afternic.com, ns4.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns3.afternic.com dns.jomax.net |
Analysis
IP Addresses
whatcould.be resolves to two IP numbers: 13.248.169.48 and 76.223.54.146.
other host names including oryginalni.com, miningpooldata.xyz, inume.com, mail.sandvich.org and joelrettew.com share IP numbers with whatcould.be.
Name Servers
whatcould.be is delegated to two name servers ns3.afternic.com and ns4.afternic.com.
whatcould.be shares the same name server setup as other domains, for instance ufcscout.com, thelady.org, omniink.com, iifjas.com and touchit.com.au.
whatcould.be at least partially shares name servers with other domains, for instance macsyourman.com, delightos.com, 42my.com, directsafety.org and commercial.glass.
These name servers are commonly used alongside verification-frsgyqgb387khmr9jzuunx.ns101.verify.hn and verification-gx9m4qbbvukhxvxdk2zdbk.ns101.verify.hn.
Host names with one IP number:
ns3.afternic.com points to 97.74.98.65
ns4.afternic.com points to 173.201.66.65