threeoclocktrain.com - dns.ninja
threeoclocktrain.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=1786083224 | ||||||
Same first word
threeoclocktrain.com |
DNS History
10 records (9 active, 1 former)
●NSdns1.sitezoogle.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●NSdns2.sitezoogle.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●MXalt1.aspmx.l.google.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●MXalt2.aspmx.l.google.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●MXaspmx.l.google.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●MXaspmx2.googlemail.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●MXaspmx3.googlemail.com2015-06-28 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
●A172.65.197.382026-08-07 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
○A192.237.132.2482015-06-28 → 2020-01-14 · 3 obs
● 2020-01-14 23:08:56
○ 2026-08-07 06:35:38
●A2606:4700:90:0:3626:d0ff:6957:de12026-08-07 → 2026-08-07 · 2 obs
● 2026-08-07 06:35:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net, h.gtld-servers.net... | - |
| threeoclocktrain.com | dns1.sitezoogle.com, dns2.sitezoogle.com | 2 records |
✅ Authoritative Response
Server:15.222.184.47
NS records: dns1.sitezoogle.com, dns2.sitezoogle.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for threeoclocktrain.com (unsigned zone)
⏱️ Timing
Total: 203ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 172.65.197.38 |
| AAAA | 1 | 2606:4700:90:0:3626:d0ff:6957:de1 |
| NS | 2 | dns1.sitezoogle.com, dns2.sitezoogle.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| SOA | 1 | dns1.sitezoogle.com info.sitezoogle.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns1.sitezoogle.com, dns2.sitezoogle.com)
Analysis
IP Addresses
threeoclocktrain.com points to the IP addresses 172.65.197.38 and 2606:4700:90:0:3626:d0ff:6957:de1
Two other host names, along with arkdarlowm.net, haroldmikesizemore.com and steveberkemeier.com, also share IP numbers with threeoclocktrain.com.
Name Servers
threeoclocktrain.com uses two name servers for its delegation: dns1.sitezoogle.com and dns2.sitezoogle.com.
threeoclocktrain.com shares its NS records with other domains, for example jesseleefalls.com, mastermuse.com, funkinsoulnuts.com and two others.
The name servers of threeoclocktrain.com overlap at least partially with those of other domains — among them seanpett.com, guisemusic.com, 27.vg and two more.
These name servers commonly appear alongside the name servers dns3.sitezoogle.com and dns4.sitezoogle.com.
Both dns1.sitezoogle.com and dns2.sitezoogle.com have a single IP address each — dns1.sitezoogle.com resolves to 15.222.184.47 while dns2.sitezoogle.com resolves to 3.98.101.147.
Mail Servers
threeoclocktrain.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 threeoclocktrain.com and other domains, including serasewing.com, ns500599.ns500724.ns500599.ns500724.ns500599.ns500724.ns500724.ns500599.ns500669.ns500669.yummyflingsfinder.com, ns500742.ns500754.ns500754.ns500731.ns500742.ns500671.ns500704.ns500705.ns500291.ns500649.ns500666.lustychickser.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.122.26 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
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 2a00:1450:400b:c02::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.