linkedin-mailserver.com - dns.ninja
linkedin-mailserver.com
| DNSSEC | ๐ Signed (DS record present) | ||||||
| NS | ns0.transip.net โญ | ||||||
| A | 2a01:7c8:dddd:195::195๐ณ๐ฑ TRANSIP-AS2a01:7c8::/32 TransIP B.V. Amsterdam IPv6 network | ||||||
| PTR | ns0.transip.net | ||||||
| A | 195.135.195.195๐ฎ๐น TRANSIP-AS195.135.195.0/24 TransIP B.V. | ||||||
| PTR | ns0.transip.net | ||||||
| NS | ns1.transip.nl | ||||||
| A | 2a01:7c8:7000:195::195๐ณ๐ฑ TRANSIP-AS2a01:7c8::/32 TransIP B.V. Amsterdam IPv6 network | ||||||
| PTR | ns1.transip.nl | ||||||
| A | 195.8.195.195๐ณ๐ฑ TRANSIP-AS195.8.195.0/24 TransIP B.V. | ||||||
| PTR | ns1.transip.nl | ||||||
| NS | ns2.transip.eu | ||||||
| A | 2a01:7c8:f:c1f::195๐ณ๐ฑ TRANSIP-AS2a01:7c8::/32 TransIP B.V. Amsterdam IPv6 network | ||||||
| PTR | ns2.transip.eu | ||||||
| A | 37.97.199.195๐ณ๐ฑ TRANSIP-AS37.97.128.0/17 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | ns2.transip.eu | ||||||
| SOA | ns0.transip.nethostmaster@transip.nl 2026-06-26 #1 | ||||||
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=1785110867 | ||||||
Same first word
linkedin-mailserver.com |
DNS History
12 records (3 active, 9 former)
โNSns0.transip.net2018-01-24 โ 2026-07-27 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โNSns1-02.azure-dns.com2026-03-01 โ 2026-03-01 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โNSns1.transip.nl2018-01-24 โ 2026-07-27 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โNSns2-02.azure-dns.net2026-03-01 โ 2026-03-01 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โNSns2.transip.eu2018-01-24 โ 2026-07-27 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โNSns3-02.azure-dns.org2026-03-01 โ 2026-03-01 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โNSns4-02.azure-dns.info2026-03-01 โ 2026-03-01 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โMXmail.informatiebeveiliging.nl2018-01-24 โ 2018-01-24 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โMXmx.safemailsvr.com2026-03-01 โ 2026-05-11 ยท 5 obs
โ 2026-03-01 04:27:46
โ 2026-05-11 11:19:58
โ 2026-06-03 04:28:44
โ 2026-07-27 00:21:38
โA20.50.224.352026-03-01 โ 2026-05-11 ยท 5 obs
โ 2026-03-01 04:27:46
โ 2026-05-11 11:19:58
โ 2026-06-03 04:28:44
โ 2026-07-27 00:21:38
โA84.243.255.462018-01-24 โ 2018-01-24 ยท 3 obs
โ 2026-03-01 04:27:46
โ 2026-07-27 00:21:38
โPTRlinkedin-mailserver.com2026-03-01 โ 2026-07-27 ยท 2 obs
โ 2026-07-27 00:21:38
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| linkedin-mailserver.com | ns1.transip.nl, ns0.transip.net, ns2.transip.eu | - |
โ Authoritative Response
Server:195.8.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: 693ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns0.transip.net, ns1.transip.nl... |
| SOA | 1 | ns0.transip.net hostmaster.transip.nl |
Analysis
Name Servers
Three name servers are authoritative for linkedin-mailserver.com: ns2.transip.eu, ns0.transip.net and ns1.transip.nl.
linkedin-mailserver.com shares at least some of its name servers with other domains, including pickeevastgoed.nl, brightonduckstore.com, nettelligence.eu and two others.
ns2.transip.eu resolves to 37.97.199.195 and 2a01:7c8:f:c1f::195. ns0.transip.net resolves to 195.135.195.195 and 2a01:7c8:dddd:195::195. ns1.transip.nl resolves to 195.8.195.195 and 2a01:7c8:7000:195::195. All three hostnames point to two IP numbers each.