V

Connect failure - perhaps firewall

Checked:
15.05.2019 16:04:25


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
api-ios.test001.pl
A
148.251.32.218
Hostname: pokaauto.pl
yes
1
0

AAAA

yes


www.api-ios.test001.pl
A
148.251.32.218
Hostname: pokaauto.pl
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(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
pl
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: 28.05.2019, 05:00:00, Signature-Inception: 15.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

3 DNSKEY RR found

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

Public Key with Algorithm 8, KeyTag 39205, Flags 256

Public Key with Algorithm 8, KeyTag 44893, Flags 256

2 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 13.06.2019, 12:00:00, Signature-Inception: 14.05.2019, 12:00:00, KeyTag 25412, Signer-Name: pl

Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 13.06.2019, 12:00:00, Signature-Inception: 14.05.2019, 12:00:00, KeyTag 39205, Signer-Name: pl

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

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

Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 25412, DigestType 2 and Digest "QPpTyx2v9DO3qNRaBaYk7P9KO9HI8UabAIouC59yGkk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
test001.pl
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


api-ios.test001.pl
0 DS RR in the parent zone found

0 DNSKEY RR found


www.api-ios.test001.pl
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.api-ios.test001.pl
  ns1.atthost.pl / srv1

api-ios.test001.pl
  ns1.atthost.pl / srv1
185.255.40.4
test001.pl
  ns1.atthost.pl / srv1


  ns2.atthost.pl / ns2.atthost.pl

pl
  a-dns.pl / Polish ccTLD infrustructure


  b-dns.pl / b-decix


  c-dns.pl


  d-dns.pl


  e-dns.pl / Polish ccTLD infrastructure


  f-dns.pl


  g-dns.pl


  h-dns.pl


  i-dns.pl


4. SOA-Entries


Domain:pl
Primary:a-dns.pl
Mail:dnsmaster.nask.pl
Serial:1557900097
Refresh:900
Retry:300
Expire:2592000
TTL:3600
num Entries:9


Domain:test001.pl
Primary:ns1.atthost.pl
Mail:root.test001.pl
Serial:2018080101
Refresh:10800
Retry:3600
Expire:1814400
TTL:3600
num Entries:2


Domain:api-ios.test001.pl
Primary:ns1.atthost.pl
Mail:root.test001.pl
Serial:2018080101
Refresh:10800
Retry:3600
Expire:1814400
TTL:3600
num Entries:1


Domain:www.api-ios.test001.pl
Primary:ns1.atthost.pl
Mail:root.test001.pl
Serial:2018080101
Refresh:10800
Retry:3600
Expire:1814400
TTL:3600
num Entries:1


5. Url-Checks


show header:
Domainname Http-StatusredirectSec.G
• http://api-ios.test001.pl/
148.251.32.218
404

0.263
M
Not Found
Server: nginx
Date: Wed, 15 May 2019 14:04:51 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 883
Connection: close
Set-Cookie: PHPSESSID=8716d1496ae1d240c692ece90a60ce23; Path=/; Domain=api-ios.test001.pl
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache

• http://www.api-ios.test001.pl/
148.251.32.218
404

0.070
M
Not Found
Server: nginx
Date: Wed, 15 May 2019 14:04:51 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 887
Connection: close
Set-Cookie: PHPSESSID=f045e30bab059cd27b7f0f8916ef8583; Path=/; Domain=www.api-ios.test001.pl
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache

• https://api-ios.test001.pl/
148.251.32.218
-2

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

• https://www.api-ios.test001.pl/
148.251.32.218
-2

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

• http://api-ios.test001.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
148.251.32.218
404

0.060
A
Not Found
Visible Content: Page Not Found The page you are looking for could not be found. Check the address bar to ensure your URL is spelled correctly. If all else fails, you can visit our home page at the link below. Visit the Home Page
Server: nginx
Date: Wed, 15 May 2019 14:04:53 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 883
Connection: close
Set-Cookie: PHPSESSID=8710d3b6747c73143da1d17d055c6293; Path=/; Domain=api-ios.test001.pl
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache

• http://www.api-ios.test001.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
148.251.32.218
404

0.057
A
Not Found
Visible Content: Page Not Found The page you are looking for could not be found. Check the address bar to ensure your URL is spelled correctly. If all else fails, you can visit our home page at the link below. Visit the Home Page
Server: nginx
Date: Wed, 15 May 2019 14:04:54 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 887
Connection: close
Set-Cookie: PHPSESSID=6d5b208a6841e3809ed297f2fdc6a05f; Path=/; Domain=www.api-ios.test001.pl
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache

6. Comments

Aname "api-ios.test001.pl" is subdomain, public suffix is "pl", top-level-domain-type is "country-code", Country is Poland, tld-manager is "Research and Academic Computer Network"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - no version with Http-Status 200
Hfatal error: No https - result with http-status 200, no encryption
Mhttp://api-ios.test001.pl/ 148.251.32.218
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttp://www.api-ios.test001.pl/ 148.251.32.218
404

Misconfiguration - main pages should never send http status 400 - 499
Vhttps://api-ios.test001.pl/ 148.251.32.218
-2

connect failure - perhaps firewall
Vhttps://www.api-ios.test001.pl/ 148.251.32.218
-2

connect failure - perhaps firewall
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: h-dns.pl: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate
AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, there must be a certificate. But the certificate may be expired or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors.
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: 29567 milliseconds, 29.567 seconds


7. Connections

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 (BETA)

1. Source CertSpotter - active certificates

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


10. Html-Content - Entries (BETA - mixed content and other checks)

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.api-ios.test001.pl
0

no CAA entry found
1
0
api-ios.test001.pl
0

no CAA entry found
1
0
test001.pl
0

no CAA entry found
1
0
pl
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
api-ios.test001.pl

ok
1
0
www.api-ios.test001.pl

ok
1
0
_acme-challenge.api-ios.test001.pl

missing entry or wrong length
1
0
_acme-challenge.www.api-ios.test001.pl

missing entry or wrong length
1
0
_acme-challenge.api-ios.test001.pl.test001.pl

perhaps wrong
1
0
_acme-challenge.api-ios.test001.pl.api-ios.test001.pl

perhaps wrong
1
0
_acme-challenge.www.api-ios.test001.pl.api-ios.test001.pl

perhaps wrong
1
0
_acme-challenge.www.api-ios.test001.pl.www.api-ios.test001.pl

perhaps wrong
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=95b9c7cd-8558-46dd-a73c-3f9979a78413


Last Result: https://check-your-website.server-daten.de/?q=api-ios.test001.pl - 2019-05-15 16:04:25


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

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