leadbuzzer.com - dns.ninja
leadbuzzer.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=1785643177 | ||||||
Same first word
leadbuzzer.nl |
leadbuzzer.com |
Similar names
DNS History
16 records (10 active, 6 former)
●NSns0.transip.net2026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
○NSns1.softlayer.com2015-06-30 → 2017-05-17 · 3 obs
● 2017-05-17 02:00:54
○ 2026-08-02 04:09:20
●NSns1.transip.nl2026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
○NSns2.softlayer.com2015-11-12 → 2017-05-17 · 4 obs
● 2015-11-12 15:31:02
● 2017-05-17 02:00:54
○ 2026-08-02 04:09:20
●NSns2.transip.eu2026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
●MXalt1.aspmx.l.google.com2015-11-12 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
●MXalt2.aspmx.l.google.com2015-11-12 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
○MXalt3.aspmx.l.google.com2015-11-12 → 2017-05-17 · 3 obs
● 2017-05-17 02:00:54
○ 2026-08-02 04:09:20
○MXalt4.aspmx.l.google.com2015-11-12 → 2017-05-17 · 3 obs
● 2017-05-17 02:00:54
○ 2026-08-02 04:09:20
●MXaspmx.l.google.com2015-11-12 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
●MXaspmx2.googlemail.com2026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
●MXaspmx3.googlemail.com2026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
○A159.122.5.1012015-06-30 → 2015-11-12 · 4 obs
● 2015-11-12 15:31:02
○ 2016-02-07 17:04:44
○ 2026-08-02 04:09:20
●A2a01:7c8:bb0a:4d6::42026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
○A37.97.136.1262016-02-07 → 2017-05-17 · 4 obs
● 2016-02-07 17:04:44
● 2017-05-17 02:00:54
○ 2026-08-02 04:09:20
●A85.10.131.2232026-08-02 → 2026-08-02 · 2 obs
● 2026-08-02 04:09:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| leadbuzzer.com | ns1.transip.nl, ns0.transip.net, ns2.transip.eu | - |
✅ Authoritative Response
Server:195.135.195.195
NS records: ns1.transip.nl, ns0.transip.net, ns2.transip.eu
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 927ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 85.10.131.223 |
| AAAA | 1 | 2a01:7c8:bb0a:4d6::4 |
| NS | 3 | ns0.transip.net, ns1.transip.nl... |
| MX | 5 | ASPMX2.GOOGLEMAIL.com (pri: 10), ASPMX3.GOOGLEMAIL.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns0.transip.net hostmaster.transip.nl |
Analysis
IP Addresses
leadbuzzer.com resolves to the IP addresses 85.10.131.223 and 2a01:7c8:bb0a:4d6::4
leadbuzzer.nl, for instance, is one of the other host names sharing IP numbers with leadbuzzer.com.
Name Servers
The authoritative name servers for leadbuzzer.com are ns2.transip.eu, ns0.transip.net and ns1.transip.nl — three in total.
leadbuzzer.com partially shares its NS delegation with several other domains, including sconsult.nl, we-energize.com, junglethebungle.com and two others.
ns2.transip.eu, ns0.transip.net and ns1.transip.nl all resolve to exactly two IP numbers apiece: ns2.transip.eu → 37.97.199.195 and 2a01:7c8:f:c1f::195; ns0.transip.net → 195.135.195.195 and 2a01:7c8:dddd:195::195; ns1.transip.nl → 195.8.195.195 and 2a01:7c8:7000:195::195.
Mail Servers
leadbuzzer.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
leadbuzzer.com shares at least some of its mail servers with other domains — for example bodeaus.com, ns500734.ns500734.ns500734.ns500693.ns500693.ns500588.ns500699.ns500693.ns500588.ns500612.ns500588.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com, ns500758.ns500758.ns500758.ns500758.ns500736.ns500735.ns500698.ns500698.ns500576.ns500698.ns500698.ns500576.ns500576.ns500652.trackreceptor.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.167.27 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.