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


 

 

V

 

Connect failure - perhaps firewall

 

Checked:
14.03.2019 17:42:43

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
simoncircle.se
A
81.231.60.74
Hostname: 81-231-60-74-no276.tbcn.telia.com
yes
1
0

AAAA

yes


www.simoncircle.se
A
81.231.60.74
Hostname: 81-231-60-74-no276.tbcn.telia.com
yes
1
0

AAAA

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16749, Flags 256






Public Key with Algorithm 8, KeyTag 19164, Flags 385






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






2 RRSIG RR to validate DNSKEY RR found






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






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






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






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: se

se
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner se., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.03.2019, 05:00:00 +, Signature-Inception: 14.03.2019, 04:00:00 +, KeyTag 16749, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 52668, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner se., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 26.03.2019, 01:53:40 +, Signature-Inception: 12.03.2019, 02:10:42 +, KeyTag 59407, Signer-Name: se






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






Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 59407, DigestType 2 and Digest "Z6jgb8792Tl/d/JsQa3k7BQvKZvPoYJ/Dvj9h/L2MCI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: simoncircle.se

simoncircle.se
0 DS RR in the parent zone found






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 2371, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 34505, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner simoncircle.se., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.04.2019, 00:39:28 +, Signature-Inception: 07.02.2019, 00:39:28 +, KeyTag 2371, Signer-Name: simoncircle.se






Status: Good - Algorithmus 13 and DNSKEY with KeyTag 2371 used to validate the DNSKEY RRSet






Error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

 

3. Name Servers

DomainNameserverNS-IP
www.simoncircle.se
  kate.ns.cloudflare.com / 67m4

simoncircle.se
  kate.ns.cloudflare.com / 67m4
173.245.58.124

 
2400:cb00:2049:1::adf5:3a7c

  trey.ns.cloudflare.com / 67m3
173.245.59.242

 
2400:cb00:2049:1::adf5:3bf2
se
  a.ns.se / s2.stu


  b.ns.se / u1.gbg


  c.ns.se / u2.svl


  f.ns.se / n1.sth


  g.ns.se / n1.ume


  i.ns.se / s2.amx


  j.ns.se / ns010b.app18.ams2.afilias-nst.info


  x.ns.se


  y.ns.se / LHR1


  z.ns.se / STO2

 

4. SOA-Entries


Domain:se
Zone-Name:
Primary:catcher-in-the-rye.nic.se
Mail:registry-default.nic.se
Serial:2019031416
Refresh:1800
Retry:1800
Expire:864000
TTL:7200
num Entries:10


Domain:simoncircle.se
Zone-Name:
Primary:kate.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2030424423
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:4


Domain:www.simoncircle.se
Zone-Name:
Primary:kate.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2030424423
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
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
• http://simoncircle.se/
81.231.60.74
200


0.053
H
Date: Thu, 14 Mar 2019 17:43:02 GMT
Server: App-webs/
ETag: "ad6-746-53c48e29"
Content-Length: 1862
Content-Type: text/html
Connection: close
Last-Modified: Tue, 15 Jul 2014 02:12:57 GMT

• http://www.simoncircle.se/
81.231.60.74
200


0.054
H
Date: Thu, 14 Mar 2019 17:43:02 GMT
Server: App-webs/
ETag: "ad6-746-53c48e29"
Content-Length: 1862
Content-Type: text/html
Connection: close
Last-Modified: Tue, 15 Jul 2014 02:12:57 GMT

• https://simoncircle.se/
81.231.60.74
-2


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

• https://www.simoncircle.se/
81.231.60.74
-2


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

• http://simoncircle.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
81.231.60.74
404


0.053
A
Not Found
Visible Content:
Date: Thu, 14 Mar 2019 17:43:05 GMT
Server: App-webs/
Content-Length: 245
Content-Type: text/html
Connection: close

• http://www.simoncircle.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
81.231.60.74
404


0.053
A
Not Found
Visible Content:
Date: Thu, 14 Mar 2019 17:43:05 GMT
Server: App-webs/
Content-Length: 245
Content-Type: text/html
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "simoncircle.se" is domain, public suffix is "se", top-level-domain-type is "country-code", Country is Sweden, tld-manager is "The Internet Infrastructure Foundation"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://simoncircle.se/ 81.231.60.74


Url with incomplete Content-Type - header - missing charset
http://www.simoncircle.se/ 81.231.60.74


Url with incomplete Content-Type - header - missing charset
http://simoncircle.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 81.231.60.74


Url with incomplete Content-Type - header - missing charset
http://www.simoncircle.se/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 81.231.60.74


Url with incomplete Content-Type - header - missing charset
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Vhttps://simoncircle.se/ 81.231.60.74
-2

Connect failure - perhaps firewall
Vhttps://www.simoncircle.se/ 81.231.60.74
-2

Connect failure - perhaps firewall

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: kate.ns.cloudflare.com: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: ok (67m4). COOKIE: no result. CLIENTSUBNET: ok.
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.

4. Content- and Performance-critical Checks

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, httpd -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, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 19797 milliseconds, 19.797 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)

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

 

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

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.simoncircle.se
0

no CAA entry found
1
0
simoncircle.se
0

no CAA entry found
1
0
se
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
simoncircle.se

ok
1
0
www.simoncircle.se

ok
1
0
_acme-challenge.simoncircle.se

Name Error - The domain name does not exist
1
0
_acme-challenge.www.simoncircle.se

Name Error - The domain name does not exist
1
0
_acme-challenge.simoncircle.se.simoncircle.se

Name Error - The domain name does not exist
1
0
_acme-challenge.www.simoncircle.se.www.simoncircle.se

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

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=5b51037d-2cab-4817-9fb3-c8077c718b7b

 

Last Result: https://check-your-website.server-daten.de/?q=simoncircle.se - 2019-03-14 17:42:43

 

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

 

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

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=simoncircle.se