signal4d.dev - robtex.com
signal4d.dev
dev
| 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 | ||||||
Subdomains
auth.signal4d.dev |
airwise-developer.signal4d.dev |
Same first word
Similar names
DNS History
17 records (9 active, 8 former)
●NSns-1087.awsdns-07.org2026-02-25 → 2026-03-03 · 2 obs
● 2026-03-03 08:33:30
●NSns-1927.awsdns-48.co.uk2026-02-25 → 2026-03-03 · 2 obs
● 2026-03-03 08:33:30
●NSns-369.awsdns-46.com2026-02-25 → 2026-03-03 · 2 obs
● 2026-03-03 08:33:30
●NSns-516.awsdns-00.net2026-02-25 → 2026-03-03 · 2 obs
● 2026-03-03 08:33:30
●MXinbound-smtp.us-west-2.amazonaws.com2026-02-25 → 2026-03-03 · 2 obs
● 2026-03-03 08:33:30
●A3.167.112.342026-02-25 → 2026-03-03 · 6 obs
● 2026-02-25 07:22:04
● 2026-02-26 20:38:46
○ 2026-02-26 21:59:08
● 2026-02-27 00:18:00
● 2026-03-03 08:33:30
●A3.167.112.542026-02-25 → 2026-03-03 · 6 obs
● 2026-02-25 07:22:04
● 2026-02-26 20:38:46
○ 2026-02-26 21:59:08
● 2026-02-27 00:18:00
● 2026-03-03 08:33:30
●A3.167.112.582026-02-25 → 2026-03-03 · 6 obs
● 2026-02-25 07:22:04
● 2026-02-26 20:38:46
○ 2026-02-26 21:59:08
● 2026-02-27 00:18:00
● 2026-03-03 08:33:30
●A3.167.112.692026-02-25 → 2026-03-03 · 6 obs
● 2026-02-25 07:22:04
● 2026-02-26 20:38:46
○ 2026-02-26 21:59:08
● 2026-02-27 00:18:00
● 2026-03-03 08:33:30
○A3.170.3.1162026-02-25 → 2026-03-03 · 2 obs
○ 2026-03-03 08:33:30
○A3.170.3.1292026-02-25 → 2026-03-03 · 2 obs
○ 2026-03-03 08:33:30
○A3.170.3.72026-02-25 → 2026-03-03 · 2 obs
○ 2026-03-03 08:33:30
○A3.170.3.702026-02-25 → 2026-03-03 · 2 obs
○ 2026-03-03 08:33:30
○A99.84.41.1152026-02-25 → 2026-02-26 · 6 obs
○ 2026-02-25 07:22:04
○ 2026-02-26 20:38:46
● 2026-02-26 21:59:08
○ 2026-02-27 00:18:00
○ 2026-03-03 08:33:30
○A99.84.41.32026-02-25 → 2026-02-26 · 6 obs
○ 2026-02-25 07:22:04
○ 2026-02-26 20:38:46
● 2026-02-26 21:59:08
○ 2026-02-27 00:18:00
○ 2026-03-03 08:33:30
○A99.84.41.502026-02-25 → 2026-02-26 · 6 obs
○ 2026-02-25 07:22:04
○ 2026-02-26 20:38:46
● 2026-02-26 21:59:08
○ 2026-02-27 00:18:00
○ 2026-03-03 08:33:30
○A99.84.41.802026-02-25 → 2026-02-26 · 6 obs
○ 2026-02-25 07:22:04
○ 2026-02-26 20:38:46
● 2026-02-26 21:59:08
○ 2026-02-27 00:18:00
○ 2026-03-03 08:33:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| signal4d.dev | ns-1927.awsdns-48.co.uk, ns-1087.awsdns-07.org, ns-369.awsdns-46.com, ns-516.awsdns-00.net | - |
✅ Authoritative Response
Server: 205.251.199.135
NS records: ns-1927.awsdns-48.co.uk, ns-1087.awsdns-07.org, ns-369.awsdns-46.com, ns-516.awsdns-00.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for signal4d.dev (unsigned zone)
⏱️ Timing
Total: 570ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 3.167.112.69, 3.167.112.34... |
| NS | 4 | ns-1087.awsdns-07.org, ns-1927.awsdns-48.co.uk... |
| MX | 1 | inbound-smtp.us-west-2.amazonaws.com (pr |
| TXT | 1 | google-site-verification=uErFShz2T-fLSwB |
| SOA | 1 | ns-369.awsdns-46.com awsdns-hostmaster.a |
Analysis
Hierarchy
signal4d.dev is a parent of auth.signal4d.dev and airwise-developer.signal4d.dev.
IP Addresses
signal4d.dev points to four IP numbers: 3.167.112.34, 3.167.112.54, 3.167.112.58 and 3.167.112.69.
Other host names, for instance bindustrialgtx.w3spaces.com, metimasklogon.w3spaces.com, actor-academy.avex.jp, dp1o10ctejmk4.cloudfront.net and www.as-me-ot.com share IP numbers with signal4d.dev.
Name Servers
signal4d.dev is delegated to four name servers: ns-369.awsdns-46.com, ns-516.awsdns-00.net, ns-1087.awsdns-07.org and ns-1927.awsdns-48.co.uk.
signal4d.dev at least partially shares name servers with other domains, for instance d20ogzan2m1wn0.cloudfront.net, d3udgcumjwwxq7.cloudfront.net, d3m7omu9lo28gq.cloudfront.net, aws.cookingchanneltv.com and nelsonang.com.
Host names with two IP numbers:
ns-369.awsdns-46.com points to: 2600:9000:5301:7100::1 and 205.251.193.113.
ns-516.awsdns-00.net points to: 2600:9000:5302:400::1 and 205.251.194.4.
ns-1087.awsdns-07.org points to: 2600:9000:5304:3f00::1 and 205.251.196.63.
ns-1927.awsdns-48.co.uk points to: 2600:9000:5307:8700::1 and 205.251.199.135.
Mail Servers
signal4d.dev is handled by a single mail server, inbound-smtp.us-west-2.amazonaws.com.
signal4d.dev uses the same mail server configuration as other domains, such as zeniainsure.com, mez100.cn, restore.openmg.com, naturulint.com and langmail.io.
signal4d.dev shares mail servers with other domains at least in part, for instance tribalparis.atlassian.net, softeam.atlassian.net, netshops.atlassian.net, hosted.atlassian.net and scoutship.jp.
These mail servers are commonly used with inbound-smtp.us-east-1.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
inbound-smtp.us-west-2.amazonaws.com resolves to four IPs: 35.161.157.106, 52.13.163.116, 52.43.162.244 and 54.188.121.70.