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




O

old / weak connection

Checked:
15.05.2019 18:22:12


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
sp.ttk.mx
A
195.49.206.243
Hostname: sp.ttk.mx
yes
1
0

AAAA

yes


www.sp.ttk.mx

Name Error
yes
1
0


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
mx
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, 15:00:00, Signature-Inception: 15.05.2019, 14: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 39767, Flags 257 (SEP = Secure Entry Point)

Public Key with Algorithm 8, KeyTag 46531, Flags 256

2 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.07.2019, 15:00:00, Signature-Inception: 02.05.2019, 15:00:00, KeyTag 39767, Signer-Name: mx

Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.06.2019, 00:00:00, Signature-Inception: 15.05.2019, 00:00:00, KeyTag 46531, Signer-Name: mx

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

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

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


sp.ttk.mx
0 DS RR in the parent zone found

0 DNSKEY RR found


www.sp.ttk.mx
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.sp.ttk.mx
  ns.strace.net

sp.ttk.mx
  ns.strace.net
195.49.200.131
ttk.mx
  ns.strace.net


  ns2.strace.net

mx
  c.mx-ns.mx


  e.mx-ns.mx / 4.fra.pch


  i.mx-ns.mx


  m.mx-ns.mx


  o.mx-ns.mx


  x.mx-ns.mx


4. SOA-Entries


Domain:mx
Primary:m.mx-ns.mx
Mail:hostmaster.nic.mx
Serial:1557936337
Refresh:900
Retry:900
Expire:604800
TTL:1800
num Entries:6


Domain:ttk.mx
Primary:ns.strace.net
Mail:postmaster.ttk.mx
Serial:2019051500
Refresh:14400
Retry:7200
Expire:604800
TTL:38400
num Entries:2


Domain:sp.ttk.mx
Primary:ns.strace.net
Mail:postmaster.ttk.mx
Serial:2019051500
Refresh:14400
Retry:7200
Expire:604800
TTL:38400
num Entries:1


5. Url-Checks


show header:
Domainname Http-StatusredirectSec.G
• http://sp.ttk.mx:8080/
195.49.206.243
200

0.160
H
Date: Wed, 15 May 2019 16:22:43 GMT
Connection: Close
Content-Type: text/html
Content-Length: 109

• https://sp.ttk.mx:8080/
195.49.206.243
200

1.330
B
Date: Wed, 15 May 2019 16:22:44 GMT
Connection: Close
Content-Type: text/html
Content-Length: 109

• http://sp.ttk.mx:8080/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
195.49.206.243
404

0.160
A
Not Found
Visible Content:
Date: Wed, 15 May 2019 16:22:45 GMT
Connection: Close

6. Comments

Aname "sp.ttk.mx" is subdomain, public suffix is "mx", top-level-domain-type is "country-code", Country is Mexico, tld-manager is "NIC-Mexico ITESM - Campus Monterrey"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Agood: one preferred version: non-www is preferred
http://sp.ttk.mx:8080/ 195.49.206.243


Url with incomplete Content-Type - header - missing charset
https://sp.ttk.mx:8080/ 195.49.206.243


Url with incomplete Content-Type - header - missing charset
Bhttps://sp.ttk.mx:8080/ 195.49.206.243
200

Missing HSTS-Header
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: 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.
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
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: ns.strace.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
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, 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. 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: 33666 milliseconds, 33.666 seconds


7. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
sp.ttk.mx
195.49.206.243
8080
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha1
error checking OCSP stapling
weak
sp.ttk.mx
195.49.206.243
8080
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha1
error checking OCSP stapling
weak
Chain - incomplete
1CN=sp.ttk.mx


8. Certificates

1.
1.
CN=sp.ttk.mx
15.05.2019
13.08.2019
11 days expired
sp.ttk.mx - 1 entry
1.
1.
CN=sp.ttk.mx
15.05.2019

13.08.2019
11 days expired
sp.ttk.mx - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03F914FB460B59476AE5DD48FA0BA0EE8266
Thumbprint:1502624B1C770AAA38E8BD559DC084E78F5ADC06
SHA256 / Certificate:CpSZOpkm2IVfQaVCeldvz68J4bI8cIthR97Kg4hCw4M=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):de6e2475d1e45948d56f868fe9bf03475ba5d29bc2ae119a5023c925a584581d
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 571 days


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
expires in 571 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 768 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 768 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no



9. Last Certificates - Certificate Transparency Log Check (BETA)

1. Source CertSpotter - active certificates

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

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
913491773
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-05-15 15:09:13
2019-08-13 15:09:13
sp.ttk.mx - 1 entries



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
sp.ttk.mx
0

no CAA entry found
1
0
ttk.mx
0

no CAA entry found
1
0
mx
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
sp.ttk.mx

ok
1
0
_acme-challenge.sp.ttk.mx

Name Error - The domain name does not exist
1
0
_acme-challenge.sp.ttk.mx.ttk.mx

Name Error - The domain name does not exist
1
0
_acme-challenge.sp.ttk.mx.sp.ttk.mx

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=53b92b1c-2ad4-4968-9e5e-0e562927aa0c


Last Result: https://check-your-website.server-daten.de/?q=sp.ttk.mx%3a8080 - 2019-05-15 18:22:12


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

<a href="https://check-your-website.server-daten.de/?q=sp.ttk.mx%3a8080" target="_blank">Check this Site: sp.ttk.mx:8080</a>