stateofthebeard.com - dns.ninja
stateofthebeard.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=1782295750 | ||||||
Same first word
stateofthebeard.com |
DNS History
9 records (9 active, 0 former)
●NSns29.domaincontrol.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●NSns30.domaincontrol.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●MXalt1.aspmx.l.google.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●MXalt2.aspmx.l.google.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●MXaspmx.l.google.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●MXaspmx2.googlemail.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●MXaspmx3.googlemail.com2026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●A15.197.225.1282026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
●A3.33.251.1682026-04-04 → 2026-06-24 · 2 obs
● 2026-06-24 10:36:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| stateofthebeard.com | ns29.domaincontrol.com, ns30.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.104.15
NS records: ns29.domaincontrol.com, ns30.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for stateofthebeard.com (unsigned zone)
⏱️ Timing
Total: 1215ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns29.domaincontrol.com, ns30.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 1 | google-site-verification=DiQWwtt5qlsnG7g |
| SOA | 1 | ns29.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns29.domaincontrol.com, ns29.domaincontrol.com, ns30.domaincontrol.com...)
Analysis
IP Addresses
stateofthebeard.com points to the IP addresses 3.33.251.168 and 15.197.225.128
Two other host names, along with ussailingschools.com, globelifegroupinc.net and edsafety.com, also share IP numbers with stateofthebeard.com.
Name Servers
stateofthebeard.com uses two name servers for its delegation: ns29.domaincontrol.com and ns30.domaincontrol.com.
stateofthebeard.com shares its NS records with other domains, for example skltranslation.com, mercroft.ca, turnpharmaceuticals.com and two others.
The two host names ns29.domaincontrol.com and ns30.domaincontrol.com each have a pair of IP addresses: ns29.domaincontrol.com has 97.74.104.15 and 2603:5:2181::f, and ns30.domaincontrol.com has 173.201.72.15 and 2603:5:2281::f.
Mail Servers
stateofthebeard.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between stateofthebeard.com and other domains, including ns500731.ns500742.ns500742.ns500754.ns500731.ns500704.ns500688.ns500678.ns500704.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500742.ns500742.ns500742.ns500671.ns500742.ns500742.ns500731.ns500671.ns500705.ns500671.ns500671.ns500291.ns500666.ns500142.lusty(0x736c7574)z.com, ns500724.ns500724.ns500724.ns500737.ns500737.ns500737.ns500737.ns500737.ns500724.ns500724.ns500724.ns500697.www.yummyflingsfinder.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.62.27 and 2607:f8b0:4004:c17::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.