Check DNS, Urls + Redirects, Certificates and Content of your Website



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
17.10.2020 23:24:01


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
rum18.linkedin.com

Name Error
yes
1
0
www.rum18.linkedin.com

Name Error
yes
1
0
*.linkedin.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.rum18.linkedin.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.11.2020, 00:00:00 +, Signature-Inception: 11.10.2020, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.10.2020, 17:00:00 +, Signature-Inception: 17.10.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26116 used to validate the DS RRSet in the parent zone



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24966, Flags 256



Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 31510, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.10.2020, 18:24:21 +, Signature-Inception: 12.10.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: linkedin.com
linkedin.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "2stn4rgf45nfgdfqbrfkgddbg65tobn8" between the hashed NSEC3-owner "2stm1fq46hmd34udrrt08nf97ukb32nq" and the hashed NextOwner "2stndeg1euelnd6lv4mos5m6cvm8l10i". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 2stm1fq46hmd34udrrt08nf97ukb32nq.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 23.10.2020, 05:00:01 +, Signature-Inception: 16.10.2020, 03:50:01 +, KeyTag 31510, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "linkedin.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 24.10.2020, 04:40:34 +, Signature-Inception: 17.10.2020, 03:30:34 +, KeyTag 31510, Signer-Name: com



0 DNSKEY RR found




Zone: rum18.linkedin.com
rum18.linkedin.com
0 DS RR in the parent zone found

Zone: www.rum18.linkedin.com
www.rum18.linkedin.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.rum18.linkedin.com
  ns1.p43.dynect.net

rum18.linkedin.com
  ns1.p43.dynect.net

linkedin.com
  dns1.p09.nsone.net / trexd-fra03-913-5405
198.51.44.9
New York/United States (US) - NSONE Inc


 
2620:4d:4000:6259:7::9
New York/United States (US) - NSONE Inc


  dns2.p09.nsone.net / trexd-fra03-386-5412
198.51.45.9
New York/United States (US) - NSONE Inc


 
2a00:edc0:6259:7::9
Enschede/Provincie Overijssel/Netherlands (NL) - NS1


  dns3.p09.nsone.net / trexd-fra03-911-5410
198.51.44.73
New York/United States (US) - NSONE Inc


 
2620:4d:4000:6259:7::90
New York/United States (US) - NSONE Inc


  dns4.p09.nsone.net / trexd-fra03-386-5409
198.51.45.73
New York/United States (US) - NSONE Inc


 
2a00:edc0:6259:7::90
Enschede/Provincie Overijssel/Netherlands (NL) - NS1


  ns1.p43.dynect.net / proxy-121-defra.hivecast-121-defra.as15135.net
208.78.70.43
New York/United States (US) - Oracle Corporation


 
2001:500:90:1::43
New York/United States (US) - Oracle Corporation


  ns2.p43.dynect.net / proxy-341-nlams2.hivecast-341-nlams2.as15135.net
204.13.250.43
New York/United States (US) - Oracle Corporation


  ns3.p43.dynect.net / proxy-113-defra.hivecast-113-defra.as15135.net
208.78.71.43
New York/United States (US) - Oracle Corporation


 
2001:500:94:1::43
New York/United States (US) - Oracle Corporation


  ns4.p43.dynect.net / proxy-134-defra.hivecast-134-defra.as15135.net
204.13.251.43
Ashburn/Virginia/United States (US) - Oracle Corporation

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1602969809
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1602969824
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:linkedin.com
Zone-Name:linkedin.com
Primary:dns1.p09.nsone.net
Mail:hostmaster.linkedin.com
Serial:1602542413
Refresh:3600
Retry:600
Expire:604800
TTL:300
num Entries:8


Domain:linkedin.com
Zone-Name:linkedin.com
Primary:ns1.p43.dynect.net
Mail:hostmaster.linkedin.com
Serial:2020101615
Refresh:3600
Retry:600
Expire:604800
TTL:300
num Entries:6


Domain:rum18.linkedin.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.rum18.linkedin.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "rum18.linkedin.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 52208 (complete: 131120)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AInfo:: 25 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers.
AInfo:: 25 Queries complete, 17 with IPv6, 8 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 3.1 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 8 different Name Servers found: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net, 8 Name Servers included in Delegation: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net, 8 Name Servers included in 1 Zone definitions: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net, 2 Name Servers listed in SOA.Primary: dns1.p09.nsone.net, ns1.p43.dynect.net.
Error: Different SOA.Primary Name Servers found, different SOA Definitions.: dns1.p09.nsone.net,ns1.p43.dynect.net.
Error: SOA.Primary Name Server not included in the delegation set.: dns1.p09.nsone.net,ns1.p43.dynect.net.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 8 Name Servers, 3 different subnets (first Byte): 198., 204., 208., 3 different subnets (first two Bytes): 198.51., 204.13., 208.78., 6 different subnets (first three Bytes): 198.51.44., 198.51.45., 204.13.250., 204.13.251., 208.78.70., 208.78.71.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2620:, 2a00:, 3 different subnets (first two blocks): 2001:0500:, 2620:004d:, 2a00:edc0:, 4 different subnets (first three blocks): 2001:0500:0090:, 2001:0500:0094:, 2620:004d:4000:, 2a00:edc0:6259:, 4 different subnets (first four blocks): 2001:0500:0090:0001:, 2001:0500:0094:0001:, 2620:004d:4000:6259:, 2a00:edc0:6259:0007:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 14 good Nameserver
AGood: Nameserver supports Echo Capitalization: 14 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 14 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.p43.dynect.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.p43.dynect.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 155637 milliseconds, 155.637 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
776485548
precert
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
2019-02-21 00:00:00
2021-02-25 12:00:00
afd.perf.linkedin.com, linkedin.com, rum14.linkedin.com, rum17.linkedin.com, rum18.linkedin.com, rum19.linkedin.com, www.linkedin.com - 7 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1224299027
precert
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
2019-02-20 23:00:00
2021-02-25 11:00:00
afd.perf.linkedin.com, linkedin.com, rum14.linkedin.com, rum17.linkedin.com, rum18.linkedin.com, rum19.linkedin.com, www.linkedin.com
7 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.p43.dynect.net, ns2.p43.dynect.net, ns3.p43.dynect.net, ns4.p43.dynect.net

QNr.DomainTypeNS used
1
net
NS
f.root-servers.net (2001:500:2f::f)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
dns1.p09.nsone.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1

Answer: dns2.p01.nsone.net
198.51.45.1

Answer: dns3.p01.nsone.net
198.51.44.65

Answer: dns4.p01.nsone.net
198.51.45.65
3
dns2.p09.nsone.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1

Answer: dns2.p01.nsone.net
198.51.45.1

Answer: dns3.p01.nsone.net
198.51.44.65

Answer: dns4.p01.nsone.net
198.51.45.65
4
dns3.p09.nsone.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1

Answer: dns2.p01.nsone.net
198.51.45.1

Answer: dns3.p01.nsone.net
198.51.44.65

Answer: dns4.p01.nsone.net
198.51.45.65
5
dns4.p09.nsone.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1

Answer: dns2.p01.nsone.net
198.51.45.1

Answer: dns3.p01.nsone.net
198.51.44.65

Answer: dns4.p01.nsone.net
198.51.45.65
6
ns1.p43.dynect.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1.dynamicnetworkservices.net, ns2.dynamicnetworkservices.net, ns3.dynamicnetworkservices.net, ns4.dynamicnetworkservices.net, ns5.dynamicnetworkservices.net, ns6.dynamicnetworkservices.net, ns7.dynamicnetworkservices.net

Answer: ns1.dynamicnetworkservices.net
2001:500:90:1::136, 208.78.70.136

Answer: ns2.dynamicnetworkservices.net
204.13.250.136

Answer: ns3.dynamicnetworkservices.net
2001:500:94:1::136, 208.78.71.136

Answer: ns4.dynamicnetworkservices.net
204.13.251.136

Answer: ns5.dynamicnetworkservices.net
162.88.60.21, 2600:2000:1000::21

Answer: ns6.dynamicnetworkservices.net
162.88.61.21, 2600:2000:1001::21

Answer: ns7.dynamicnetworkservices.net
108.59.165.1, 2a02:e180:8::1
7
ns2.p43.dynect.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1.dynamicnetworkservices.net, ns2.dynamicnetworkservices.net, ns3.dynamicnetworkservices.net, ns4.dynamicnetworkservices.net, ns5.dynamicnetworkservices.net, ns6.dynamicnetworkservices.net, ns7.dynamicnetworkservices.net

Answer: ns1.dynamicnetworkservices.net
2001:500:90:1::136, 208.78.70.136

Answer: ns2.dynamicnetworkservices.net
204.13.250.136

Answer: ns3.dynamicnetworkservices.net
2001:500:94:1::136, 208.78.71.136

Answer: ns4.dynamicnetworkservices.net
204.13.251.136

Answer: ns5.dynamicnetworkservices.net
162.88.60.21, 2600:2000:1000::21

Answer: ns6.dynamicnetworkservices.net
162.88.61.21, 2600:2000:1001::21

Answer: ns7.dynamicnetworkservices.net
108.59.165.1, 2a02:e180:8::1
8
ns3.p43.dynect.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1.dynamicnetworkservices.net, ns2.dynamicnetworkservices.net, ns3.dynamicnetworkservices.net, ns4.dynamicnetworkservices.net, ns5.dynamicnetworkservices.net, ns6.dynamicnetworkservices.net, ns7.dynamicnetworkservices.net

Answer: ns1.dynamicnetworkservices.net
2001:500:90:1::136, 208.78.70.136

Answer: ns2.dynamicnetworkservices.net
204.13.250.136

Answer: ns3.dynamicnetworkservices.net
2001:500:94:1::136, 208.78.71.136

Answer: ns4.dynamicnetworkservices.net
204.13.251.136

Answer: ns5.dynamicnetworkservices.net
162.88.60.21, 2600:2000:1000::21

Answer: ns6.dynamicnetworkservices.net
162.88.61.21, 2600:2000:1001::21

Answer: ns7.dynamicnetworkservices.net
108.59.165.1, 2a02:e180:8::1
9
ns4.p43.dynect.net
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1.dynamicnetworkservices.net, ns2.dynamicnetworkservices.net, ns3.dynamicnetworkservices.net, ns4.dynamicnetworkservices.net, ns5.dynamicnetworkservices.net, ns6.dynamicnetworkservices.net, ns7.dynamicnetworkservices.net

Answer: ns1.dynamicnetworkservices.net
2001:500:90:1::136, 208.78.70.136

Answer: ns2.dynamicnetworkservices.net
204.13.250.136

Answer: ns3.dynamicnetworkservices.net
2001:500:94:1::136, 208.78.71.136

Answer: ns4.dynamicnetworkservices.net
204.13.251.136

Answer: ns5.dynamicnetworkservices.net
162.88.60.21, 2600:2000:1000::21

Answer: ns6.dynamicnetworkservices.net
162.88.61.21, 2600:2000:1001::21

Answer: ns7.dynamicnetworkservices.net
108.59.165.1, 2a02:e180:8::1
10
dns1.p09.nsone.net: 198.51.44.9
A
dns1.p01.nsone.net (198.51.44.1)
11
dns1.p09.nsone.net: 2620:4d:4000:6259:7::9
AAAA
dns1.p01.nsone.net (198.51.44.1)
12
dns2.p09.nsone.net: 198.51.45.9
A
dns1.p01.nsone.net (198.51.44.1)
13
dns2.p09.nsone.net: 2a00:edc0:6259:7::9
AAAA
dns1.p01.nsone.net (198.51.44.1)
14
dns3.p09.nsone.net: 198.51.44.73
A
dns1.p01.nsone.net (198.51.44.1)
15
dns3.p09.nsone.net: 2620:4d:4000:6259:7::90
AAAA
dns1.p01.nsone.net (198.51.44.1)
16
dns4.p09.nsone.net: 198.51.45.73
A
dns1.p01.nsone.net (198.51.44.1)
17
dns4.p09.nsone.net: 2a00:edc0:6259:7::90
AAAA
dns1.p01.nsone.net (198.51.44.1)
18
ns1.p43.dynect.net: 208.78.70.43
A
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
19
ns1.p43.dynect.net: 2001:500:90:1::43
AAAA
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
20
ns2.p43.dynect.net: 204.13.250.43
A
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
21
ns2.p43.dynect.net: No AAAA record found
AAAA
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
22
ns3.p43.dynect.net: 208.78.71.43
A
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
23
ns3.p43.dynect.net: 2001:500:94:1::43
AAAA
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
24
ns4.p43.dynect.net: 204.13.251.43
A
ns1.dynamicnetworkservices.net (2001:500:90:1::136)
25
ns4.p43.dynect.net: No AAAA record found
AAAA
ns1.dynamicnetworkservices.net (2001:500:90:1::136)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
linkedin.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
linkedin.com

ok
1
0
_acme-challenge.rum18.linkedin.com.linkedin.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=500bf1b5-2c4e-43b5-83ba-2d29b36a2cde


Last Result: https://check-your-website.server-daten.de/?q=rum18.linkedin.com - 2020-10-17 23:24:01


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=rum18.linkedin.com" target="_blank">Check this Site: rum18.linkedin.com</a>