blastwaves.com - dns.ninja
blastwaves.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=1783855262 | ||||||
Previously MX for
blastwaves.com |
Same first word
blastwaves.com |
DNS History
14 records (10 active, 4 former)
●NSns1.geodns.net2007-10-29 → 2026-07-12 · 2 obs
● 2026-07-12 11:23:38
●NSns2.geodns.net2007-10-29 → 2026-07-12 · 2 obs
● 2026-07-12 11:23:38
●MXalt1.aspmx.l.google.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
●MXalt2.aspmx.l.google.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
●MXaspmx.l.google.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
●MXaspmx2.googlemail.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
●MXaspmx3.googlemail.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
●MXaspmx4.googlemail.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
●MXaspmx5.googlemail.com2015-07-05 → 2026-07-12 · 3 obs
● 2015-07-05 14:12:40
● 2026-07-12 11:23:38
○MXblastwaves.com2007-10-29 → 2007-10-29 · 3 obs
○ 2015-07-05 14:12:40
○ 2026-07-12 11:23:38
○A207.198.127.742016-12-02 → 2016-12-02 · 4 obs
● 2016-12-02 05:17:26
○ 2026-03-30 00:24:36
○ 2026-07-12 11:23:38
●A45.79.99.552026-03-30 → 2026-07-12 · 3 obs
● 2026-03-30 00:24:36
● 2026-07-12 11:23:38
○A72.51.35.92007-10-29 → 2007-10-29 · 3 obs
○ 2015-07-05 14:12:40
○ 2026-07-12 11:23:38
○A72.51.43.242015-07-05 → 2016-04-09 · 5 obs
● 2015-07-05 14:12:40
● 2016-04-09 19:33:44
○ 2016-12-02 05:17:26
○ 2026-07-12 11:23:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, d.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net... | - |
| blastwaves.com | ns2.geodns.net, ns1.geodns.net | - |
✅ Authoritative Response
Server:69.90.13.6
NS records: ns2.geodns.net, ns1.geodns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for blastwaves.com (unsigned zone)
⏱️ Timing
Total: 530ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.79.99.55 |
| NS | 2 | ns1.geodns.net, ns2.geodns.net |
| MX | 7 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 20)... |
| TXT | 1 | v=spf1 a mx ip4:209.85.215.174 ip4:207.1 |
| SOA | 1 | ns1.geodns.net goldram.attglobal.net |
Analysis
IP Addresses
blastwaves.com resolves to just one IP address, 45.79.99.55.
Two other host names, along with firstchoiceair.com, centeroflongevitymedicine.com and dpmgpo.com, also share IP numbers with blastwaves.com.
Name Servers
blastwaves.com uses two name servers for its delegation: ns1.geodns.net and ns2.geodns.net.
blastwaves.com shares its NS records with other domains, for example brianandterri.com, partgopher.com, zadoodie.com and two others.
At least some of blastwaves.com's name servers are shared with other domains, for example 182.34.64.in-addr.arpa, 179.34.64.in-addr.arpa, kalyxcenter.org and two more.
The name servers ns1.peer1.net, ns2.peer1.net, sb1.construnet.com.br and two others are commonly seen in use alongside these name servers.
Each of ns1.geodns.net and ns2.geodns.net has one IP address: ns1.geodns.net uses 69.90.13.5 and ns2.geodns.net uses 69.90.13.6.
Mail Servers
blastwaves.com uses 7 mail servers for delivery: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
There is at least a partial MX overlap between blastwaves.com and other domains, including ns500795.ns500794.ns500821.ns500794.ns500795.ns500794.ns500794.ns500821.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, chinawalkingclub.com, ns500758.ns500759.ns500759.ns500758.ns500708.ns500698.ns500576.ns500708.ns500576.ns500576.ns500652.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, aspmx.l.google.com, alt1.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::1b.
aspmx4.googlemail.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
aspmx5.googlemail.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.
aspmx.l.google.com directs traffic to 192.178.218.26 and 2607:f8b0:4004:c1d::1a.
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::1a.
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.