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




V

Connect failure - perhaps firewall

Checked:
13.05.2019 17:59:31


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
lurboa.com
A
159.203.165.5
No Hostname found
yes
1
0

AAAA

yes


www.lurboa.com
A
159.203.165.5
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



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 25266, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.06.2019, 00:00:00, Signature-Inception: 11.05.2019, 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



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.05.2019, 05:00:00, Signature-Inception: 13.05.2019, 04:00:00, KeyTag 25266, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.05.2019, 18:25:33, Signature-Inception: 12.05.2019, 18:20:33, 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: lurboa.com
lurboa.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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





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


3. Name Servers

DomainNameserverNS-IP
www.lurboa.com
  ns-cloud-e1.googledomains.com

lurboa.com
  ns-cloud-e1.googledomains.com
216.239.32.110

 
2001:4860:4802:32::6e

  ns-cloud-e2.googledomains.com
216.239.34.110

 
2001:4860:4802:34::6e

  ns-cloud-e3.googledomains.com
216.239.36.110

 
2001:4860:4802:36::6e

  ns-cloud-e4.googledomains.com
216.239.38.110

 
2001:4860:4802:38::6e
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
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1557763144
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


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


Domain:lurboa.com
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:25
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.lurboa.com
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:25
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:1


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://lurboa.com/
159.203.165.5
302
https://lurboa.com/
0.207
A
Content-Type: text/html; charset=utf-8
Location: https://lurboa.com/
Date: Mon, 13 May 2019 16:00:08 GMT
Content-Length: 42
Connection: close

• http://www.lurboa.com/
159.203.165.5
302
https://www.lurboa.com/
0.207
A
Content-Type: text/html; charset=utf-8
Location: https://www.lurboa.com/
Date: Mon, 13 May 2019 16:00:08 GMT
Content-Length: 46
Connection: close

• https://lurboa.com/
159.203.165.5
-4

4.556
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream.

• https://www.lurboa.com/
159.203.165.5
-2

2.597
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 159.203.165.5:443

• http://lurboa.com:443/
159.203.165.5
-2

1.310
A
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 159.203.165.5:443
Visible Content:

• http://lurboa.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
159.203.165.5
-2

2.607
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 159.203.165.5:80
Visible Content:

• http://www.lurboa.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
159.203.165.5
-2

1.307
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 159.203.165.5:80
Visible Content:

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "lurboa.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
CError - no version with Http-Status 200
Hfatal error: No https - result with http-status 200, no encryption
Vhttp://lurboa.com:443/ 159.203.165.5
-2

connect failure - perhaps firewall
Vhttps://www.lurboa.com/ 159.203.165.5
-2

connect failure - perhaps firewall
Vhttp://lurboa.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.165.5
-2

connect failure - perhaps firewall
Vhttp://www.lurboa.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.165.5
-2

connect failure - perhaps firewall
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
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.
http://lurboa.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.165.5
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.lurboa.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 159.203.165.5
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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: 52604 milliseconds, 52.604 seconds


7. Connections (http/2- and additional Tls.1.0/1.1/1.2 checks are BETA)

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow.

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
941346615
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-12 17:24:27
2019-02-10 17:24:27
sso.lurboa.com
1 entries


941169640
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-12 15:58:49
2019-02-10 15:58:49
accounts.lurboa.com, ssl.lurboa.com
2 entries


933240972
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-09 19:18:18
2019-02-07 19:18:18
www.lurboa.com
1 entries



10. Html-Content - Entries

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.lurboa.com
0

no CAA entry found
1
0
lurboa.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
lurboa.com

ok
1
0
www.lurboa.com

ok
1
0
_acme-challenge.lurboa.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.lurboa.com

Name Error - The domain name does not exist
1
0
_acme-challenge.lurboa.com.lurboa.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.lurboa.com.lurboa.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.lurboa.com.www.lurboa.com

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=f51f5c1f-e057-4486-ba73-4ece52252016


Last Result: https://check-your-website.server-daten.de/?q=lurboa.com - 2019-05-13 17:59:31


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

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