relevantbits.com - dns.ninja
relevantbits.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=1783753447 | ||||||
Subdomains
context.relevantbits.com |
Same first word
relevantbits.com |
relevantbits.net |
Similar names
DNS History
20 records (10 active, 10 former)
●NSns-1015.awsdns-62.net2026-02-16 → 2026-07-11 · 3 obs
● 2026-02-16 09:35:14
● 2026-07-11 07:05:06
●NSns-1042.awsdns-02.org2026-02-16 → 2026-07-11 · 3 obs
● 2026-02-16 09:35:14
● 2026-07-11 07:05:06
●NSns-108.awsdns-13.com2026-02-16 → 2026-07-11 · 3 obs
● 2026-02-16 09:35:14
● 2026-07-11 07:05:06
●NSns-1578.awsdns-05.co.uk2026-02-16 → 2026-07-11 · 3 obs
● 2026-02-16 09:35:14
● 2026-07-11 07:05:06
○NSns03.domaincontrol.com2015-08-07 → 2016-07-04 · 4 obs
● 2016-07-04 12:13:48
○ 2017-02-12 06:08:16
○ 2026-07-11 07:05:06
○NSns04.domaincontrol.com2015-08-07 → 2016-07-04 · 4 obs
● 2016-07-04 12:13:48
○ 2017-02-12 06:08:16
○ 2026-07-11 07:05:06
○NSns1.wordpress.com2019-12-29 → 2019-12-29 · 4 obs
● 2019-12-29 08:34:50
○ 2026-02-16 09:35:14
○ 2026-07-11 07:05:06
○NSns2.wordpress.com2019-12-29 → 2019-12-29 · 4 obs
● 2019-12-29 08:34:50
○ 2026-02-16 09:35:14
○ 2026-07-11 07:05:06
○NSns3.wordpress.com2019-12-29 → 2019-12-29 · 4 obs
● 2019-12-29 08:34:50
○ 2026-02-16 09:35:14
○ 2026-07-11 07:05:06
●MXalt1.aspmx.l.google.com2019-12-29 → 2026-07-11 · 6 obs
● 2019-12-29 08:34:50
● 2026-06-01 19:36:18
○ 2026-06-05 19:33:54
● 2026-06-07 06:20:32
● 2026-07-11 07:05:06
●MXalt2.aspmx.l.google.com2019-12-29 → 2026-07-11 · 6 obs
● 2019-12-29 08:34:50
● 2026-06-01 19:36:18
○ 2026-06-05 19:33:54
● 2026-06-07 06:20:32
● 2026-07-11 07:05:06
●MXalt3.aspmx.l.google.com2019-12-29 → 2026-07-11 · 6 obs
● 2019-12-29 08:34:50
● 2026-06-01 19:36:18
○ 2026-06-05 19:33:54
● 2026-06-07 06:20:32
● 2026-07-11 07:05:06
●MXalt4.aspmx.l.google.com2019-12-29 → 2026-07-11 · 6 obs
● 2019-12-29 08:34:50
● 2026-06-01 19:36:18
○ 2026-06-05 19:33:54
● 2026-06-07 06:20:32
● 2026-07-11 07:05:06
●MXaspmx.l.google.com2019-12-29 → 2026-07-11 · 6 obs
● 2019-12-29 08:34:50
● 2026-06-01 19:36:18
○ 2026-06-05 19:33:54
● 2026-06-07 06:20:32
● 2026-07-11 07:05:06
○MXmailstore1.secureserver.net2015-08-07 → 2016-07-04 · 4 obs
● 2016-07-04 12:13:48
○ 2017-02-12 06:08:16
○ 2026-07-11 07:05:06
○MXsmtp.secureserver.net2015-08-07 → 2016-07-04 · 4 obs
● 2016-07-04 12:13:48
○ 2017-02-12 06:08:16
○ 2026-07-11 07:05:06
○A192.0.78.1912019-12-29 → 2019-12-29 · 4 obs
● 2019-12-29 08:34:50
○ 2026-02-16 09:35:14
○ 2026-07-11 07:05:06
○A192.0.78.1932019-12-29 → 2019-12-29 · 4 obs
● 2019-12-29 08:34:50
○ 2026-02-16 09:35:14
○ 2026-07-11 07:05:06
●A23.227.38.652026-02-16 → 2026-07-11 · 6 obs
● 2026-02-16 09:35:14
● 2026-06-01 19:36:18
○ 2026-06-05 19:33:54
● 2026-06-07 06:20:32
● 2026-07-11 07:05:06
○A50.63.202.522015-08-07 → 2016-07-04 · 4 obs
● 2016-07-04 12:13:48
○ 2017-02-12 06:08:16
○ 2026-07-11 07:05:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| relevantbits.com | ns-108.awsdns-13.com, ns-1015.awsdns-62.net, ns-1578.awsdns-05.co.uk, ns-1042.awsdns-02.org | 2 records |
✅ Authoritative Response
Server:205.251.195.247
NS records: ns-108.awsdns-13.com, ns-1015.awsdns-62.net, ns-1578.awsdns-05.co.uk, ns-1042.awsdns-02.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for relevantbits.com (unsigned zone)
⏱️ Timing
Total: 500ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.65 |
| NS | 4 | ns-1015.awsdns-62.net, ns-1042.awsdns-02.org... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | MS=9814124AC610E8E6EDC6E03927EE5D2010179, google-site-verification=IiX5LWUZ4Hm3Jj1... |
| SOA | 1 | ns-108.awsdns-13.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-108.awsdns-13.com, ns-108.awsdns-13.com)
Analysis
Hierarchy
The domain context.relevantbits.com falls under the parent relevantbits.com.
IP Addresses
relevantbits.com has exactly one IP address — 23.227.38.65.
beefexclusief.nl, hopdream.com, heimat-gin.de plus two other host names have IP numbers in common with relevantbits.com.
Name Servers
Four name servers handle the delegation for relevantbits.com: ns-108.awsdns-13.com, ns-1015.awsdns-62.net, ns-1042.awsdns-02.org and ns-1578.awsdns-05.co.uk.
At least some of relevantbits.com's name servers are shared with other domains, for example 242.83.99.in-addr.arpa, sabinatimpea.com, htlchennai.com and two more.
Four hostnames, each resolving to a pair of IP addresses: ns-108.awsdns-13.com directs to 205.251.192.108 and 2600:9000:5300:6c00::1; ns-1015.awsdns-62.net directs to 205.251.195.247 and 2600:9000:5303:f700::1; ns-1042.awsdns-02.org directs to 205.251.196.18 and 2600:9000:5304:1200::1; ns-1578.awsdns-05.co.uk directs to 205.251.198.42 and 2600:9000:5306:2a00::1.
Mail Servers
Five mail servers handle relevantbits.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by relevantbits.com are shared with other domains: wearebrainstorm.com, daviddu.com, pawsmauritius.org and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt1.aspmx.l.google.com directs traffic to 142.250.102.27 and 2a00:1450:4025:402::1b.
alt2.aspmx.l.google.com directs traffic to 192.178.213.27 and 2a00:1450:4013:c1e::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.
Both aspmx.l.google.com and alt3.aspmx.l.google.com resolve to 2a00:1450:4009:c0f::1a IP addresses each.